Can someone with a clean windows build test the changes for the libxml/iconv linking. I believe it is working, but have so many copies of libxml/libxslt on my system I cant be 100% sure that it is.
A few things. It currently is exporting all libxml symbols. It looks like there may be about 200K difference if we only export those we need, so any opinions on full or partial export? Also still trying to libxml to include all iconv symbols so that iconv is not needed in php4dllts.dsp to export its symbols. Not sure if this is necessary as compiler may be optimizing out the redundant functions. For Edin's builds we are going to need to seperate libs for the branches as these wont work with php 4 - libxml may, but libxslt wont as its static build is now linked dynamically against libxml. www.ctindustries.net/patches/winphplibxml.zip contains the libxml, libxslt as well as iconv files for building. iconv is the stock version, but is included for versioning. libxml.dll and libxslt/libexslt dlls are not needed, as we only need the static libs, but are included. php_libxml2.def needs to be placed in the ext/libxml directory. libxml is version 2.5.11, libxslt is version 1.0.33 and iconv is version 1.8 http://www.ctindustries.net/patches/winlibxml.diff.txt diff is only for the debug build right now. iconv.dsp was changed to link against php4ts_debug.lib for its iconv symbols. Seems to work though there's still an open bug (#26194) so the iconv() function isnt working. xsl.dsp was changed to link against php4ts_debug.lib for its libxml and iconv symbols php4dllts.dsp statically links against libxml and iconv. Edin, hopefully this is what you were looking for. Rob -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
