Svennson, thank you for your passionate response; I think we have already reached a consensus on the issue of semantics. On the issue of compiling, it is not the lack of documentation for the compiler which is preventing me from compiling a suitable php_gd2.dll, but rather the instructions for compiling that dll itself. I am using Visual C++ 6.0 and plan on upgrading to Visual Studio .NET 2003 soon. I realize that the GDlib requires the FreeType, libjpeg, and libpng libraries (libpng itself requires zlib). After having tried this, the dll is missing about 40KB of data and is missing many, if not all, references to zlib when decompiled. I used the latest versions of the libraries at gnuwin32.sourceforge.net. I suspect that the zlib.lib file in the win32build folder needs to be of the same version as the zlib package, but it's only a guess. Anyway, it would be a waste to be discussing all this when there is no resolution to the problem, right? Well, according to the bug report, someone posted this: "I mentioned this to Thomas Boutell when I learned about it; GD_Lib 2.0.18 is expected to use a semicolon ';' as path separator instead of a space." I'm not sure if this is true, but if it is, thanks to whomever did this on the PHP users' behalf. I actually suggested to Thomas in an email that GDlib use a semicolon as the listseparator, modeled after its use as a path separator in Windows. So, I guess the issue is soon to be resolved, except now I'm hoping for an explanation on how to compile the php_gd2.dll for Windows. I would highly appreciate it if you or anyone else on the list would list the appropriate steps for compiling php_gd2.dll for Windows using Visual C++/Studio for 6.0 and/or .NET. --- "Svensson, B.A.T. (HKG)" <B.A.T.Svensson@lumc.nl> wrote: > I don't feel for argue about this. > > You asked the readers of this list for a comments on > weather you were > correct or not on weather your bug report was a true > bug or not. It is quit > obviouse that it is not a bug report. Its more like > a "request for change". > Period. > > > On your problems with the lack of documentation for > compiling DLL's: > > If you have such a poor compiler documentation which > does not tell you how > to use feature X when you need to, then I would > suggest you to change to a > compiler wich actually tells you how to do that - > for instance Borland C/C++ > or MS C++ devstudio. > > Another way would be to specify which compiler you > use and just ask here on > how to do it. > __________________________________ Do you Yahoo!? Find out what made the Top Yahoo! Searches of 2003 http://search.yahoo.com/top2003 -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
