[GRASS-dev] Re: bundling wxpython - solves 6.4 digitizer problem

[William Kyngesburye]

On Sep 21, 2009, at 1:09 PM, Michael Barton wrote:

>> The site-packages python path will have whichever wx path that was
>> loaded last at the top of the path list, which may or may not be the
>> one you want. (if there are multiple wxpythons installed, and  
>> assuming
>> that they were installed such that earlier installations aren't
>> trashed by later installations, which is what the official installers
>> do)
>
> Where can I check this?
>
There would be other versioned wx folders in /usr/local, with partial  
contents (stuff not directly installed by the installer will be left,  
like script-installed stuff).

Also, make sure there is only one wx path file in your site-packages,  
that points to your only installed wx.

> This fixes the 6.5 map element freezing bug too.
>
> This suggests that it is definitely something in the compiling bug.
>
> Any chance it could be something introduced with the architecture  
> arguments (which don't seem to be working correctly anyway) or with  
> any additions/updates to the bundling stuff?
>
All these new optios do is automate what you've done in the past with  
CFLAGS and LDFLAGS, and make sure that architectures are not compiled  
for wx stuff that are not available (ie when you build a 64bit GRASS).

-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/

"Mon Dieu! but they are all alike.  Cheating, murdering, lying,  
fighting, and all for things that the beasts of the jungle would not  
deign to possess - money to purchase the effeminate pleasures of  
weaklings.  And yet withal bound down by silly customs that make them  
slaves to their unhappy lot while firm in the belief that they be the  
lords of creation enjoying the only real pleasures of existence....

- the wisdom of Tarzan