| Re: [AD] Re: updated fix.bat to simplify MSVC target |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Re: updated fix.bat to simplify MSVC target
- From: guilt <karthikkumar@xxxxxxxxxx>
- Date: Sat, 2 Apr 2005 17:53:30 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Fqe6EFUDD04XgfyqhJHbMiywAzpxZM4UEV6Xw23ZAFr6ZeUNRr+fPspa9nYWL6YXIlamBexGGLbq3wxOIblp1dgWM3E9FLfxVSobhosfk0CoSUNghtQ3zFARb8lMUHOVgp31c5knue9NdVOG44D3ki+2E4xUB7z7NW+f9KAZd/Y=
makes sense. :) IMHO we just use these variables for
copying/installation purposes only.. I always set MSVCDIR to an
external directory like E:\DEV\EXT so i'll get my common includes/libs
copied into the directory ...
On Apr 2, 2005 1:22 AM, Matthew Leverton <meffer@xxxxxxxxxx> wrote:
> A minor correction. The first file didn't check to see if MSVC was the target.
>
> Which leads me to a question I have been meaning to propose... Would
> it make sense to convert the paths for every build? I know normally
> that a variable like MINGDIR doesn't have spaces, but it could. Is
> there any reason (beside that) why we limit the conversion to MSVCDir?
>
> --
> Matthew Leverton
> http://www.allegro.cc
>
>
>
--
Karthik
http://guilt.bafsoft.net