[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] MSVC 8 cl flags
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Fri, 19 Aug 2005 17:24:23 -0500
- 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=RWoyJGa8hN3mM2qFYtjvuLUpqaAw4T4JWYPI8xLJI17eyf8LvAllg2MgCyfx7ffEqzn2YnWswvCyUnFiIegfNyAeDNiqs2s9JcM/4nKXw64oV9F9muT2rs6Odl6d82szk1o+MD7NJD4AlIaf17m3CFwkjZPem4Dvg2JbD/oRPHo=
> > For MSVC 6 and MSVC 7, the /GB flag is default so it doesn't really
> > need to be there anyway. (According to the /? help anyway.)
>
> IMHO there is no problem with removing /GB
>
I didn't think there was either, but I wasn't sure if the docs can be
trusted. ;)
> > Second, tons of standard things are deprecated. To suppress those
> > warnings, the "/wd4996" switch should be used. However, it is not
> > present on MSVC6, so it can only be added on the MSVC7 and later
> > targets.
>
> I'm not sure if there is some possible way of msvc version detection,
> however easiest would be probably to add new msvc8 option.
>
I think adding a MSVC 8 target would be the best approach, because
other things might come up. However, it could be added to the MSVC 7
target because it supports /wd as well.
--
Matthew Leverton