Re: WIN32 symbol definition in rules\makefile_defs_msvc.bkl
Vaclav Slavik <[email protected]> Thu, 04 Mar 2010 07:24:57 +0100
| Newsgroups | gmane.comp.sysutils.bakefile.devel |
|---|---|
| Message-ID | <1267683897.12529.6.camel@localhost> |
--===============0135487757881609248== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-wCl9z4E4wP93/Szbbohs" --=-wCl9z4E4wP93/Szbbohs Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2010-03-03 at 22:11 +0000, Francesco Montorsi wrote: > The definition of symbol WIN32 is not really required since the cl > compiler automatically defines the _WIN32 symbol on 32 bit platforms > and both the _WIN32 and _WIN64 symbols on 64 bit platforms... > should this be considered a bakefile bug which has to be fixed (by > removing the relative <define>WIN32</define> line) ?=20 Not so fast. The reason these are defined is -- if memory serves -- that VC++ "native", manually created projects, define it. So Bakefile does it to generate as native projects as possible [*], and msvc format does it to be fully compatible with the project files. So while yes, I think we can remove them safely, I'd prefer to do exactly what native projects do (unless it would be too complicated to implement, in which case just remove WIN32 definition). Do you know what do manually created projects do in this regard? Also, does the resource compiler define _WIN32 too? Regards, Vaclav [*] Vadim in particular is quite vocal about having this property. --=-wCl9z4E4wP93/Szbbohs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEABECAAYFAkuPUjkACgkQxDYa/UZSZMkYQACfe4ZTxm1hw8/BJaWP4uOm1R78 EUYAni7M88OdjdAKClI5fioOPDJMfdVa =ZtYa -----END PGP SIGNATURE----- --=-wCl9z4E4wP93/Szbbohs-- --===============0135487757881609248== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev --===============0135487757881609248== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bakefile-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bakefile-devel --===============0135487757881609248==--