hi,

FYI, any decent VC version supports only one mode: threaded. This mess
is a 12 year old pain (vc6) :)

As for the makefile, we can have one makefile for all VC versions. I
use one for the php builds. It is on my todos to cleanup and document
it so it can be merged in curl.

Cheers,

On Tue, Feb 17, 2009 at 11:05 PM, Joe Nardone <jnardone_at_gmail.com> wrote:
>>> I noticed there are no MD(d), MT(d) suffixes at the end of targets' names
>>> neither in Makefile.vc* makefiles nor in the VC project file curllib.vcproj.
>>> Do you avoid this VC naming convention by any purpose?
>>
>> I think nobody of those who added the targets in the first place was aware
>> of any such naming convention and then the rest of the targets were added to
>> following the existing convention.
>>
>> If you ask me, we need to get something other to fix this
>> windows-build-hell. Adding 2041 different makefile targets for all sorts of
>> build config combinations doesn't feel sane. But then there's no
>> "configure"-like standard tool or so for Windows so I don't really know what
>> this other and better way would involve! :-/
>
> I don't think there's much choice. This is the tactic that both OpenSSL
> and Boost take, for example, generating 6 or 8 different outputs for the
> various permutations (static vs. shared, debug vs. release, single vs.
> multithread).
> I don't know how much I'd call it a convention, but there is
> precedence. Of course,
> they do use different naming schemes...
>
> Joe
>

-- 
Pierre
http://blog.thepimp.net | http://www.libgd.org