Re: Opinions on filesystem mount

       From: Andrew Valencia <vandys@cisco.com>
       Subject: Re: Opinions on filesystem mount

> Couple issues mixed in here. When building from a source tree, you almost
> always want the source tree to use relative paths, so you can have multiple

  VPATH is actually the easiest way to do this.

> source trees, or do something weird in a source tree without impacting the
> "regular" tools. Thus, within the VSTa source I hope always to have things
> like -L../../libc and never an absolute path.
 
  Use VPATH, (supported by gmake), and have the value of VPATH be
configurable. Ultimately, I was planning to add configuration to VSTa so
I can port VSTa to the m68k. (which I'd like to do bad)

> This leaves the question of where to place the "installed" binaries. Using
> the /lib and /bin paths can easily clash with other DOS C compiler

  All GNU tools currently default to installing in /usr/local/{bin,lib}. Why
not just use that ? We use --prefix to change the installed paths. If all
the tools and utilities for VSTa used this --prefix value, then they'd all
be in sync and work. DJGPP (if you use binaries) comes pre-configured
for a path, but we can always reconfig/build DJGPP. Also, GCC_EXEC_PREFIX
can also make DJGPP work when it's installed in a non-standard place. When I
finish porting GCC to VSTa (in progress) then we can install the "i386-vsta-gcc"
anywhere.

> environments. What if I added "make install" targets to the makefiles and
> placed the results in /vsta/lib and /vsta/bin (and /vsta/etc)? This would

  Yes. "make install" can use the value of $prefix (from configuring) and then
should install them at that value. I'll gladly discuss GNU configuration
and build techniques for hours... :-)

        - rob -
Received on Tue Apr 5 10:16:25 1994