[Zlib-devel] Use autoconf for zlib?

[Enrico Weigelt]

* Cosmin Truta <cosmin at cs.toronto.edu> schrieb:

Hi folks,

<snip>

> I see.  Well, zlib package maintainers on various systems do build the
> shared zlib, either by running the supplied configure/Makefile directly,
> or by using their own scripts. It is their job that gets easier if they
> send you the magic incantation required to build the shared library,
> that you can add to $LDSHARED and friends in configure.

I don't think we should have this front line between developers
and package maintainers. If the package itself is able to build 
properly, the job of a package maintainer remains at just define
some variables (ie. dirs) and press enter :)
Fixes by package maintainers should go to the upstream ASAP
(IMHO they legitimate hotfix releases).

<snip>

> > and the inability to make a shared and static library at the 
> > same time.
> 
> That can be easily fixed.  Maybe I can do it over this weekend, or maybe
> next weekend.  The idea is to build .o files from .c files using the
> static build settings, and to build .pic.o files from .c files using the
> shared build settings ($SFLAGS).  This way, the object files can
> coexist, and you can build both the static and the shared libs as
> separate targets.

I don't think we should maintain this all by hand.
But this doesn't necessarily has to mean, autotools are the best way.

I'm currently developing an completely new buildsystem, which is 
*not* rule-based, but strictly declarative approach. The developer
only specifies a module (ie. library) with several parameters and
the source files - not more. All the rest is done entirely by the
buildsystem.

See attachement for the zlib buildfile.


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	rsync://sources.metux.de/metux-patches
---------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pi-build.xml
Type: text/xml
Size: 2768 bytes
Desc: not available
URL: <http://madler.net/pipermail/zlib-devel_madler.net/attachments/20060420/ab0e41cb/attachment.xml>