Robin Garner wrote:
> Olaf Wagner <wagner@[EMAIL PROTECTED]
> wrote in
> news:HpE3zF.y3u@[EMAIL PROTECTED]
>
> > Robin Garner <robin.garner@[EMAIL PROTECTED]
> wrote:
> >
> >
> > ./do-cm3-std.sh buildlocal
> > sudo ./do-cm3-std.sh build****p
> ...
> > Probably the installation notes are not as clear about the semantics
of
> > build, ****p, and build****p as they should.
> >
>
> Thanks Olaf, it all works much better now - it seemed natural to assume
> that "build****p" was the same as "build" followed by "****p". Now I can
> build my system, but only after some hacking of m3makefiles. Using
> include_dir seems to crash the build system.
>
> In the m3makefile, I have
>
> include_dir("../../lib/src"), to share a handful of common modules
between
> the 3 programs that comprise my system. If I compile with the
m3makefiles
> as written, I get
>
> % cm3
> --- building in SOLgnu ---
>
> ***
> *** runtime error:
> *** Exception "PathnamePosix.CheckedRuntimeError" not in RAISES list
> *** file "../src/os/POSIX/PathnamePosix.m3", line 98
> ***
>
> Abort (core dumped)
> %
>
> but copying the contents of ../lib/src to ./src and splicing
> ../lib/src/m3makefile into src/m3makefile, it all compiles and builds
just
> fine.
>
> Any ideas ?
>
> Thanks in advance,
> Robin
What I do to share the common files among the programs for my research is
include a symbolic link in the "src" directory. The m3makefile in that
directory contains "include_dir ("COMMON")". COMMON is a symbolic link to
"../../COMMON".
I am using the SRC compiler, not pm3 or cm3. If I tried your approach
with
the SRC compiler, I do not recall. I think I am using the symbolic link
approach because it works and it was the first to come to mind.
Carl C. Hoff
|
