| Re: [AD] proposing a new official .lib name for VC static CRT version |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] proposing a new official .lib name for VC static CRT version
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Sat, 14 Jan 2006 13:47:44 -0600
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ldQmpvNz4FXHMef1VK6dDJMA+prl8FS0odHMLW00biDRzyWNatmkC9Zd5TWpf+2ibG6sj2/FmfjkHHVug8w/lnbxr6qSDrIm47Wbr9OiFMQ+b5yhMftFTCjxDnqFxv1r/jfFdAdVFdq0zOITwCiL2tsLU/eiztw8dLqASEdw3vE=
On 1/12/06, Peter Wang <tjaden@xxxxxxxxxx> wrote:
> On 2006-01-10, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
> > Yes, people would have to compile their add-ons the same way. That's
> > why I am suggesting a different name for the static runtime version.
> > As Allegro works now, two incompatible versions of the library are
> > built using the same library name.
>
> Different names for incompatible builds is a good idea.
>
Let's say I did this:
ifdef STATICRUNTIME
VERSION := $(VERSION)_srt
endif
That would yield alleg_srt, alleg_s_srt, etc. (Rather ugly names, I
know.) Anyway, (regardless of the exact names chosen) this would
require that six new obj/msvc/$VERSION folders be created. Is there
any clean way of just doing a "mkdir" at the beginning of compile
versus shipping with twelve empty msvc obj folders?
--
Matthew Leverton