> > automake creates a bunch of system-dependent soft-links:
> >
> > depcomp -> /usr/share/automake-1.7/depcomp*
> > install-sh -> /usr/share/automake-1.7/install-sh*
> > missing -> /usr/share/automake-1.7/missing*
> > mkinstalldirs -> /usr/share/automake-1.7/mkinstalldirs*
> >
> > When I ./confi
On 06 Jul 2004 00:29:39 +1000, Scott Smedley wrote:
>
> > Out of tree builds should work. If not, then it is a bug.
> >
> > For example, this should work:
> >
> > cd /nfs/cvs/fvwm
> > aclocal
> > autoheader
> > automake -a
> > autoconf
> >
> > cd /build/mysystem
> > /nfs/cvs/fvwm/
Hi Mikhael, :)
> Out of tree builds should work. If not, then it is a bug.
>
> For example, this should work:
>
> cd /nfs/cvs/fvwm
> aclocal
> autoheader
> automake -a
> autoconf
>
> cd /build/mysystem
> /nfs/cvs/fvwm/configure [params]
> make
> make install
>
> Just tried th
On 02 Jul 2004 14:51:19 +1000, Scott Smedley wrote:
>
> Is it possible to build FVWM in separate directories?
> ie. a bit like how GCC is built.
>
> I'd like to have a NFS-mounted directory with CVS source code
> & then build it for several systems.
Out of tree builds should work. If not, then i
Is it possible to build FVWM in separate directories?
ie. a bit like how GCC is built.
I'd like to have a NFS-mounted directory with CVS source code
& then build it for several systems.
SCoTT. :)
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "un
