List Info

Thread: Building wxWidgets + wxPython 2.9




Building wxWidgets + wxPython 2.9
country flaguser name
United States
2007-09-05 22:43:49
Is there an updated version of the build instructions for wxPython 2.9 ?

I did manage to get this going many moons ago by following the 2.8 instructions, but that was when everything was in CVS and, I think, a single repository.

Now I can't figure out for the life of me how to make it work. ;

My C++ has all been done in VC (and lately XCode) so I have no clue how to diagnose let alone fix makefile problems.

Any help would be gratefully received.

Cheers

Gareth
Re: Building wxWidgets + wxPython 2.9
country flaguser name
United States
2007-09-06 15:42:35
Gareth Simpson wrote:
> Is there an updated version of the build instructions
for wxPython 2.9 ?

Not yet.

> 
> I did manage to get this going many moons ago by
following the 2.8 
> instructions, but that was when everything was in CVS
and, I think, a 
> single repository.
> 
> Now I can't figure out for the life of me how to make
it work. 
> 
> My C++ has all been done in VC (and lately XCode) so I
have no clue how 
> to diagnose let alone fix makefile problems.

There have been some changes, but nothing too major.  For
the most part 
it is basically the same as before.  As you've noticed the
wx and 
wxPython trees are separate now, but the wxPython part of
the build 
should work if you put the wxPython source tree in the old
position or 
if it is a sibling dir to the wxWidgets dir.  In other
words, it can 
either be:

	.../wxWidgets
	.../wxWidgets/wxPython

or:

	.../wxWidgets
	.../wxPython

Or you can set an WXDIR environment variable to tell
wxPython where the 
wx source tree is at.

The other big change that will alter the build instructions
is that you 
don't need to build the contribs libs any more, stc has been
moved into 
the core source tree, and gizmos has its own copy of the
needed C++ 
code.  So you can ignore all the stuff about the contribs
and just use 
plain make and make install.


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


------------------------------------------------------------
---------
To unsubscribe, e-mail: wxPython-dev-unsubscribelists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-helplists.wxwidgets.org


Re: Building wxWidgets + wxPython 2.9
country flaguser name
United States
2007-09-07 10:56:11
Thanks,

That seemed to work fine right up to the point where I tried to run something with it.

Then I got the following error:

Gs-Mac:~/Perforce/DVDx/Development/Regionalization/3.0.0/src g$ python RegTool.py
Traceback (most recent call last):
&nbsp; File "RegTool.py", line 7, in <module>
&nbsp; &nbsp; import wx
 ; File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.9.0-mac-unicode/wx/__init__.py", line 45, in <module>
&nbsp; &nbsp; from wx._core import *
  File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.9.0-mac-unicode/wx/_core.py", line 4, in <module>
&nbsp; &nbsp; import _core_
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.9.0-mac-unicode/wx/_core_.so, 2): Symbol not found: __ZNK14wxOutputStream12GetClassInfoEv
&nbsp; Referenced from: /Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/wx-2.9.0-mac-unicode/wx/_core_.so
  Expected in: dynamic lookup


Is there anything that I might have obviously done wrong?

I did the whole thing including the use of swig if that makes any difference.

Cheers

Gareth




Robin Dunn wrote:
alldunn.com" type="cite">Gareth Simpson wrote:
Is there an updated version of the build instructions for wxPython 2.9 ?

Not yet.


I did manage to get this going many moons ago by following the 2.8 instructions, but that was when everything was in CVS and, I think, a single repository.

Now I can't figure out for the life of me how to make it work.
My C++ has all been done in VC (and lately XCode) so I have no clue how to diagnose let alone fix makefile problems.

There have been some changes, but nothing too major.&nbsp; For the most part it is basically the same as before.&nbsp; As you've noticed the wx and wxPython trees are separate now, but the wxPython part of the build should work if you put the wxPython source tree in the old position or if it is a sibling dir to the wxWidgets dir.  In other words, it can either be:

 &nbsp;  .../wxWidgets
 &nbsp;  .../wxWidgets/wxPython

or:

 &nbsp;  .../wxWidgets
 &nbsp;  .../wxPython

Or you can set an WXDIR environment variable to tell wxPython where the wx source tree is at.

The other big change that will alter the build instructions is that you don't need to build the contribs libs any more, stc has been moved into the core source tree, and gizmos has its own copy of the needed C++ code.  So you can ignore all the stuff about the contribs and just use plain make and make install.



[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )