Re: Solaris and socket library

Thank you for sharing your configuration. I will definitely look more closely at these macros. John Ling - Original Message - From: Russ Allbery <[EMAIL PROTECTED]> Date: Friday, January 16, 2004 6:55 pm Subject: Re: Solaris and socket library > John Ling <[EMAIL PROTECTED]> writes: >

Re: Solaris and socket library

Thank you Bob for that very useful bit of knowledge. John Ling - Original Message - From: Bob Friesenhahn <[EMAIL PROTECTED]> Date: Friday, January 16, 2004 5:14 pm Subject: Re: Solaris and socket library > This is an Autoconf issue, not Automake. Adding the following > line to > your

EXTRA_DIST and external or outside directories

Is there a way to include a directory which is external or outside of the $(top_srcdir) and which is not involved in the build process? I tried putting the following in my Makefile.am: EXTRA_DIST = $(top_srcdir)/../../perl $(top_srcdir)/../../java But, when I do a 'make dist' it does not attemp

Re: Principles of a developing from a dist or install?

- Original Message - From: Tom Tromey <[EMAIL PROTECTED]> Date: Friday, January 2, 2004 10:46 pm Subject: Re: Principles of a developing from a dist or install? > >>>>> "John" == jling <[EMAIL PROTECTED]> writes: > > I can't say wh

Principles of a developing from a dist or install?

Sorry for asking this seemingly confusing question. In my mind, if I distribute a package for which I expect other users to possibly work on the source code to enhance it, certainly the best thing would be for them to develop on the code as it exists just after it is unpacked from the tarball d

Re: SUBDIR_OBJECTS option

ECTS option > >>>>> "John" == jling <[EMAIL PROTECTED]> writes: > > John> I read in one thread the mention of a SUBDIR_OBJECTS option > in > John> automake. Supposedly this would prevent intermediate object > files from > John>

SUBDIR_OBJECTS option

I read in one thread the mention of a SUBDIR_OBJECTS option in automake. Supposedly this would prevent intermediate object files from ending up in the directory of the Makefile (I'm trying to use a non- recursive Makefile.am). Where and how is this option to be specified? Thanks, John Ling

Re: include_HEADERS and all-am

Hi Andreas, yes I did try that as well. In that case, I got: *** No rule to make target `all'. Stop. John - Original Message - From: Andreas Schwab <[EMAIL PROTECTED]> Date: Tuesday, December 23, 2003 7:36 am Subject: Re: include_HEADERS and all-am > [EMAIL PROTECTED] writes: > > >

include_HEADERS and all-am

Given my Makefile.am: AM_CPPFLAGS = -I$(srcdir)/../inc lib_LIBRARIES = libtest.a libtest_a_SOURCES = test.cpp test.hpp This works fine. Now I add to the end of that: include_HEADERS = test.hpp Now I get a make error: make[2]: *** No rule to make target 'test.hpp', needed by `all-am'. Stop.

Re: vpath builds and include paths

Thank you Bob, that suggestion worked. Also, using $(srcdir) also worked. John - Original Message - From: Bob Friesenhahn <[EMAIL PROTECTED]> Date: Monday, December 22, 2003 10:04 am Subject: Re: vpath builds and include paths > On Mon, 22 Dec 2003 [EMAIL PROTECTED] wrote: > > > Howeve

vpath builds and include paths

I was doing a test where I am using GNU automake and autoconf. I have a directory structure such as: /test Makefile.am configure.in /test/project1 Makefile.am /test/project1/sublevel Makefile.am /test/project1/sublevel/src myproj.cpp Makefile.am /test/project1/s