Setting different debug and release locations

Hi, I've just started trying to use autoconf et. al. to build my source code. The tree was previously partially autoconfed. I want to be able to use separate libraries for debug and release builds. Is this something that can be done easily? I've just thought that I could try using --prefix to do

Re: Setting different debug and release locations

Hi again, Eric Blake wrote: > According to Dan Smithers on 10/30/2008 3:47 AM: >> Hi, >> I've just started trying to use autoconf et. al. to build my source >> code. The tree was previously partially autoconfed. > >> I want to be able to use separate libraries

Re: Setting different debug and release locations

Hi > I think what Eric meant was > > cd /path/to/your/project > make dist-clean > mkdir release_build > cd release_build > ../configure [RELEASE_OPTIONS] > cd .. > mkdir debug_build > cd debug_build > ../configure [DEBUG_OPTIONS] That's what I'm doing now and everything nearly works as I want it

Setting up auto conf

Hi, I have a project that I want to convert to autoconf and I'm looking for a guide on how to set it up. The project is made up of some libraries and related executables. It needs to be built for several different architectures including Linux 2.4, Linux 2.6, Win XP and embedded. My goal is to b

Re: Setting up auto conf

Thanks Eric. The tutorial was great. > According to Dan Smithers on 1/5/2009 5:01 AM: >> My goal is to be able to set up parallel debug and release builds for >> the different architectures. > > Yes, that is provided by VPATH builds, provided by Automake. > >> I

Can't repeat build.

Hi, I have a strange problem with my autotools setup. I have configure.ac in the top directories and Makefile.am in all source directories and top directories. I use a sequence autoreconf --install cd build ../configure make Sometime this works fine. On other occasions I get an error automak

Re: Can't repeat build.

Thanks for the reply Ralph, >> I have configure.ac in the top directories and Makefile.am in all source >> directories and top directories. >> >> I use a sequence >> >> autoreconf --install >> cd build >> ../configure >> make >> >> Sometime this works fine. On other occasions I get an error >> >>

Re: Can't repeat build.

Hi Ralph, thanks for the help. > Also, I am a bit confused about when to use $(srcdir) and $(top_builddir). >>> Well, imagine instead of >>> cd build >>> ../configure >>> >>> I would do >>> >>> mkdir /dev/shm/build >>> cd /dev/shm/build >>> /path/to/configure >> I think that this

Re: Can't repeat build.

>>> BOOSTDIR=[/vol/build/boost_1_37_0] >> For eventual other users of your package, this should not be hard-coded >> but made configurable. > > I think that it can be overridden in the call to > /configure BOOSTDIR= I'v just checked and it can't be done this way - presumably this needs to be done

Re: Can't repeat build.

>>> I think that it can be overridden in the call to >>> /configure BOOSTDIR= >> I'v just checked and it can't be done this way - presumably this needs >> to be done before autoreconf is run. I can't find a way to add an >> argument to autoreconf. > > Why add it to autoreconf? The simplest would

Re: Can't repeat build.

Ralf Wildenhues wrote: > * Dan Smithers wrote on Fri, Jan 23, 2009 at 03:22:18PM CET: >>>>>> bin_PROGRAM=exec >>>>>> exec_SOURCES=exec.c >>>>>> exec_LDADD=$(top_builddir)/../libname/src/.libs -lname >>>>> Please replace thi

Adding an external project to autoconf

Hi, I am trying to add an external project to my autoconf setup. Specifically it is zlib, and that already has its own autoconf setup. I want to be able to pass the compiler to use and extra directives that are needed to the existing configuration. I have added it as an extra directory to the top

Re: Adding an external project to autoconf

Thanks for the quick response, Alfred M. Szmidt wrote: > Please see `(autoconf) Subdirectories' in the manual. That was where I started: I already use AC_CONFIG_SUBDIRS (zlib compression boost_ext) AC_OUTPUT([Makefile]) in the top level configure.ac and SUBDIRS= zlib compression boost_ext in

Re: Adding an external project to autoconf

Alfred M. Szmidt wrote: > The sub-projects must contain all generated files. That is, > autoreconf will not traverse anything listed in AC_CONFIG_SUBDIRS > (which it probobly should though). Do those directories contain > Makefile.in, configure, etc? The zlib sub-project contains a pre-generated

Re: Adding an external project to autoconf

Keith Marshall wrote: > On Wednesday 09 September 2009 18:12:02 Ralf Wildenhues wrote: >> And yes, it is perfectly possible to have subpackages that do not >> use Automake, or do not use Autoconf either. Their configure >> scripts merely have to conform to what the GNU Coding Standards >> say, and

Re: Adding an external project to autoconf

thanks >> How can I tell autoconf to run the configure without worrying about it? > > AC_CONFIG_SUBDIRS([zlib]) > > will cause zlib/configure to be run if it exists in the source tree. I had been using AC_CONFIG_SUBDIRS(zlib dir1 dir2) I never really worked out whether there is any difference

Specifying which shell to use

Is there a way of specifying the shell to ues when running the configure scripts? I see that the default configure begins #! /bin/sh that specifies to use sh. On my Ubuntu system, this is a link to /bin/dash. If I edit configure by hand to start #! /bin/bash it works. If I leave it pointing

Re: Specifying which shell to use

Original Message Subject: Re: Specifying which shell to use Date: Mon, 12 Oct 2009 14:31:25 +0100 From: Dan Smithers To: Ralf Wildenhues References: <4ace03d0.8080...@astraguard.com> <20091008183536.gb11...@gmx.de> Hi all, My supposition comes from these facts