Richard Levitte - VMS Whacker wrote: > > I've looked at util/mk1mf.pl and wondered for a long time why it does > it's own configuration stuff (from all the util/pl/*.pl files) instead > of relying on data created by Configure. When one looks in Configure, > one can find entries for the Windows targets all right, but with no C > flags or anything like that. Those things are instead in the > util/pl/*.pl files. > > This can be terribly confusing when one tries to find out what options > are actually used in a build. Too many places to look around in. > > Is there any reason for this? If not, I'll work on unifying this (not > immediately, however). >
No reason at all. Now I come to think of it a lot of that stuff could be unified or called directly from the Configure script and do things in a more standard way such as writing the Windows makefile to "Makefile" at the top level like all the others. Then you could do something like: perl Configure VC-WIN32 nmake and it would work or say... perl Configure VC-WIN32-debug nmake On the subject of Windows builds I had this idea of generating VC++ workspaces automagically by getting a perl script to get dev studio to create one of the beasts using OLE. This is left as an exercise to the reader :-) Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Gemplus: http://www.gemplus.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
