Re: Compiling wxPython in debug for windows x64

Thanks Robin! 

After reading your response, my first approach was to figure out how I 
could get it to compile with wxUSE_IFF set to zero. I thought the system 
was designed to make it easy to flip such things on and off. But as I did 
it, it involved changing code I wasn't comfortable changing to make sure 
SIP files weren't compiled/linked. That felt wrong, since you're saying 
that you explicitly turn it on, and implied that any failure to compile was 
unexpected.

So I went back and took another approach. I *thought* I was working with a 
pristine copy of wxPython with zero changes from us integrated into it 
earlier. But when I tried a different method designed to make 100% sure I 
was building from a pristine copy of wxPython, it turned out that wxPython 
actually does build without errors in debug on windows. So the problem was, 
in fact, on our end after all. Something went wrong with the integration of 
the latest fixes into our codebase.

Anyway, our problem is resolved. I appreciate your time!

Chris



On Saturday, March 3, 2018 at 9:31:13 PM UTC-6, Robin Dunn wrote:
>
>
>
> On Tuesday, February 27, 2018 at 3:54:19 PM UTC-8, Chris Helvig wrote:
>>
>> We are trying to upgrade from 4.0.0a3 to 4.0.1, and now I am unable to 
>> build wxPython in debug, due to a compile failure in wxIFFHandler. 
>>
>> Here's what it looks like when I run the command that fails:
>>
>>
>> D:\projects\ctg\main\ctg\src\vendor\PythonExtensions\wxPython>D:\projects\ctg\main\ctg\src\vendor\PythonExtensions\wxPython\..\..\python\PCBuild\amd64\python.exe 
>> .\build.py --nodoc --debug build_py
>> Will build using: 
>> "D:\projects\ctg\main\ctg\src\vendor\python\PCBuild\amd64\python.exe"
>> 3.5.2 (default, Dec  1 2016, 18:54:08) [MSC v.1900 64 bit (AMD64)]
>> Python's architecture is 64bit
>> cfg.VERSION: 4.0.1
>>
>> Running command: build_py
>> Checking for 
>> D:\projects\ctg\main\ctg\src\vendor\PythonExtensions\wxPython\bin\waf-1.7.15-p1...
>> MSVC: C:\Program Files (x86)\Microsoft Visual Studio 
>> 14.0\VC\BIN\amd64\cl.exe
>> "D:\projects\ctg\main\ctg\src\vendor\python\PCBuild\amd64\python.exe" 
>> D:\projects\ctg\main\ctg\src\vendor\PythonExtensions\wxPython\bin\waf-1.7.15-p1 
>> --debug --msvc_arch=x64 
>> --python="D:\projects\ctg\main\ctg\src\vendor\python\PCBuild\amd64\python.exe" 
>> --out=build/waf/3.5/x64/debug configure build
>>
>>
>> And it compiles some stuff, and eventually, I get down to this:
>>
>>
>> [202/885] cxx: sip\cpp\sip_corewxIdManager.cpp -> 
>> build\waf\3.5\x64\debug\sip\cpp\sip_corewxIdManager.cpp.3.o
>> sip_corewxIFFHandler.cpp
>> d:\projects\ctg\main\ctg\src\vendor\pythonextensions\wxpython\sip\cpp\sip_corewxiffhandler.cpp(22): 
>> error C2039: 'wxIFFHandler': is not a member of '`global namespace''
>> d:\projects\ctg\main\ctg\src\vendor\pythonextensions\wxpython\sip\cpp\sip_corewxiffhandler.cpp(22): 
>> error C2504: 'wxIFFHandler': base class undefined
>> d:\projects\ctg\main\ctg\src\vendor\pythonextensions\wxpython\sip\cpp\sip_corewxiffhandler.cpp(55): 
>> error C2039: 'wxIFFHandler': is not a member of '`global namespace''
>> d:\projects\ctg\main\ctg\src\vendor\pythonextensions\wxpython\sip\cpp\sip_corewxiffhandler.cpp(56): 
>> error C2614: 'sipwxIFFHandler': illegal member initialization: 
>> 'wxIFFHandler' is not a base or member
>> d:\projects\ctg\main\ctg\src\vendor\pythonextensions\wxpython\sip\cpp\sip_corewxiffhandler.cpp(73): 
>> error C3083: 'wxIFFHandler': the symbol to the left of a '::' must be a type
>>
>>
>> Plus a bunch more errors, but the problem is obviously that 
>> sip_corewxIFFHandler.cpp doesn't see wxIFFHandler. But only for debug. 
>> Release builds fine, apparently.
>>
>> I tried to find a way to compile out support for IFF format, but I can't 
>> understand the build system well enough to figure out how to do that. Every 
>> file I've tried to modify seems like it's actually built from code that 
>> exists somewhere else.
>>
>> Any ideas?
>>
>>
> The only way that the wxIFFHandler could be absent is if wxUSE_IFF is set 
> to 0 in wxWidgets/include/wx/msw/setup.h, but wxPython's build explicitly 
> sets it to 1 so I'm not sure what could have happened. But this will give 
> you a direction to look for the solution, hopefully it will help.
>
> --
> Robin Dunn
> Software Craftsman
> http://wxPython.org <http://wxpython.org/>
>  
>

-- 
You received this message because you are subscribed to the Google Groups "wxPython-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.