Improving builds script

[email protected] ("Pierre Joye")
Newsgroups php.internals.win
Message-ID <[email protected]>
HI,

I finally began to work on php itself (was porting/testing all deps)
and my first task is to make our work easier and safer when it comes
to build releases or snapshots.

The first addition is the configuration summary, it lists the enabled
extensions or SAPI and tells if an extension is shared or static. More
info is coming to allow a per extension list, so it will be easy to
see if something is missing in an extension (like ssl support in ldap,
jpeg missing in gd or whatever else) as well as a list of the
libraries used by the build and the paths info (lib, include, extra,
pecl, etc.).

As the lists are available internally as array the next step is to
create a script to automatically validate a configure call for a given
task (like a release must have all exts built).

I also fixed many problems related to extensions dependency. For many
extensions it is not possible anymore to get them enabled when a
required extension dependency is missing. All extensions should be
fixed by the end of the day.

The last fix I'll work on today is to mark an extension as disabled
when an error occurred (missing lib or headers for example). What we
had now was a disabled extension but PHP_[EXTNAME] was still set to
"yes", bringing all kind of issues during the compilation or at
runtime (wrong defines).

let me know if you like to add more things or if I do stupid things
and broke half of your builds :)

Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.