Kristján, I started to investigate the WINVER warnings that are scattered throughout the VS 2005 build. This patch eliminates them but I may have overlooked the intentions of the #include ordering. If this invalid, please let me know. Patch attached. Joseph Armbruster Kristján Valur Jónsson wrote: > >> -----Original Message----- >> From: python-dev-bounces+kristjan=ccpgames.com at python.org >> The PCbuild8 solution needs to be corrected. A patch is attached. >> > Thanks, I'll apply it. > >> In addition, I noticed that under C++/Advanced Properties, all the >> configurations appear to be set to "Compile as C++ Code" with the /TP >> argument. Should these be set to "Compile as C Code" with the /TC >> argument? > > Interesting. I hadn't noticed. I investigated, and this is the default > value for all projects. However, if you click a single .c file and > check its properties, you will find that it gets the /TC flag in its > advanced settings. So each file will be correctly compiled. (you can > confirm this by checking the command line). Removing the /TP flag from > the project settings also results in the disappearance of the per-file > /TC setting. > Very curious. In end effect, the C files are compiled as such and there > is no need for panic. > > Cheers, > Kristján > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: warnings.patch Url: http://mail.python.org/pipermail/python-dev/attachments/20070526/f967d431/attachment-0001.asc
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4