[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: seeking advice for a modular build system

From: Hans-Christoph Steiner
Subject: Re: seeking advice for a modular build system
Date: Tue, 11 Mar 2008 10:04:11 -0400

Ah, ok, I think I figured out what you mean. I wasn't clear with my initial description. What I want to enable and disable with flags is not which libraries are used for the building (i.e. --with) but which Pure Data libraries get built.

Basically, the Pure Data project has about 30ish different libraries, each with its own dependencies, named things like 'gem', 'pdp', 'zexy', etc. I want to be able to do this:

./configure --disable-pdp

Then it will build all of the Pure Data libs except 'pdp'. Also, 'pdp' depends on a lot of other libraries, so it should enable/ disable 'pdp' based on which libraries are present in the system.

Does that make sense? I don't think it's a common arrangement, but not so unusual.


On Mar 11, 2008, at 8:59 AM, Robert Boehne wrote:

There are probably too many to name, but what I played with most recently was
FreeTDS on SourceForge which does most of these things.

Hans-Christoph Steiner wrote:

Do you know of an example of the automake/libtool stuff that you are thinking of?


On Mar 10, 2008, at 4:29 PM, address@hidden wrote:

This shouldn't be much trouble. To enable or disable libraries on the command line you would probably use an Automake conditional, and AC_ARG_WITH to turn it on or off.

Automake & Libtool together will create generic LDFLAGS as well as library-specific ones automatically.

 -------------- Original message ----------------------
From: Hans-Christoph Steiner <address@hidden>

Hey all,

I am starting the process of creating an autotools build system for
Pd-extended, a large distro of a program called Pure Data and many
libraries.  Pure Data is a realtime visual programming language for
sound, video, etc.  Over the years, there have been quite a few
libraries written for it.  Currently, I have a big hacked Makefile
that builds all of the libraries. I would like to replace this with
an autotools system.

One thing that I would love to have is flags to ./configure to enable/
disable the inclusion of different libraries.  The libraries are
currently in subdirs named with the library name. I am wondering how
to best to that with autotools.

Another thing, each of the libraries are made up of
one .so/.dylib/.dll for each objectclass.  I am wondering what the
best method for having separate CFLAGS and LDFLAGS for each library.
I want to do that in case different libraries depend on different
versions of the same lib.  Perhaps I need some kind of recursive ./
configure system.

Thanks in advance!


------------------------------------------------------------------- -----

                   ¡El pueblo unido jamás será vencido!

Autoconf mailing list

--------------------------------------------------------------------- -------

"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore

Autoconf mailing list

------------------------------------------------------------------------ ----

All information should be free.  - the hacker ethic

reply via email to

[Prev in Thread] Current Thread [Next in Thread]