[wxPython-dev] Errors on embedded platform

Robin Dunn robin at alldunn.com
Mon Nov 12 15:33:16 PST 2007


Robin Dunn wrote:
> Markus Kuhnla wrote:
>> Hello wxPython experts,
>>
>> this is my very first message to this list and sorry for the 
>> circumstance that it is a question. I count on your mercy ;-)
>>
>> I try to make wxPython programs running on a Mips-based embedded 
>> platform and therefore I need to get wxPython cross-compiled and 
>> running for this platform.
>>
>> The platform is a uclibc-Linux built with a "buildroot" derived 
>> cross-toolkit. Python is version 2.4.2. I got both wxWidgets 2.8.6 and 
>> wxPython 2.8.6 cross-compiled but as soon as I try to do a 
>> "myApp=wx.App()" I get an "segmentation fault" error. I debugged this 
>> out to happen at the call to XOpenDisplay() in function 
>> wxPyTestDisplayAvailable() (helpers.cpp).

I just took another look at wxPyTedtDisplayAvailable and it calls 
XOpenDisplay with a NULL parameter, so there shouldn't be any troubles 
with converting from unicode values as I initially guessed.  The docs 
say, "On a POSIX-conformant system, if the display_name is NULL, it 
defaults to the value of the DISPLAY environment variable." so it should 
be allowed, but I suppose if your embedded platform is using a 
non-standard X it could be a problem.  You might try replacing that NULL 
with getenv("DISPLAY") to see if it makes any difference.


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!





More information about the wxpython-dev mailing list