Building gnus in separate directory

Building gnus in separate directory

[Linus Nordberg]

Hi,

When configuring gnus in other dir than the source dir, building
texi/gnus fails because makeinfo can't find gnus-faq.texi, @include'd
in gnus.texi.

Couldn't we simply make a symlink into the build directory before
building texi/gnus?

--linus

Index: configure.in
===================================================================
RCS file: /usr/local/cvsroot/gnus/configure.in,v
retrieving revision 5.1
diff -c -p -c -r5.1 configure.in
*** configure.in	1998/08/29 17:42:59	5.1
--- configure.in	2000/05/26 19:38:15
***************
*** 1,6 ****
--- 1,7 ----
  AC_INIT(lisp/gnus.el)
  AC_SET_MAKE
  AC_PROG_INSTALL
+ AC_PROG_LN_S
  AM_PATH_LISPDIR
  AC_PATH_PROG(MAKEINFO, makeinfo, no)
  AC_OUTPUT(Makefile lisp/Makefile texi/Makefile)
Index: Makefile.in
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/Makefile.in,v
retrieving revision 5.9
diff -c -p -c -r5.9 Makefile.in
*** Makefile.in	2000/05/01 12:21:43	5.9
--- Makefile.in	2000/05/26 19:40:39
*************** INSTALL = @INSTALL@
*** 19,24 ****
--- 19,27 ----
  INSTALL_DATA = @INSTALL_DATA@
  SHELL = /bin/sh
  PAPERTYPE=a4
+ LN_S = @LN_S@
+ #FIXME: Use LN_S to symlink $(srcdir)/gnus-faq.texi to build dir before 
+ #       making gnus.
  
  all: gnus message emacs-mime
  

Re: Building gnus in separate directory

[Norbert Koch]

Linus Nordberg <linus@swox.se> writes:

> Couldn't we simply make a symlink into the build directory before
> building texi/gnus?

Hmm, AFAIK, this would fail under Windows, because it doesn't know
about symlinks. Then again, it's still possible to copy the source
tree and to build in the new location.

norbert.
-- 
..  I think I'll KILL myself by leaping out of this
 14th STOREY WINDOW while reading ERICA JONG'S poetry!!

Re: Building gnus in separate directory

[Linus Nordberg]

Norbert Koch <norbert@s.netic.de> wrote
28 May 2000 09:00:07 +0200:

   Hmm, AFAIK, this would fail under Windows, because it doesn't know
   about symlinks. Then again, it's still possible to copy the source
   tree and to build in the new location.
   
The Autoconf AC_PROG_LN_S macro takes care of setting LN_S to
something that works.

--linus