BUILD/INSTALL Confusion

You made the configure, make, make install of the wxWidgets with
prefix=/usr.
Is this correct?

I only put prefix=/usr in the configure, of course:

wxPython$ ../configure --prefix=/usr --with-gtk --with-gnomeprint
--with-opengl --enable-debug --enable-geometry --enable-sound --with-sdl
--enable-display --disable-debugreport --enable-unicode

Then

make
make -C contrib/src/animate
make -C contrib/src/gizmos
make -C contrib/src/sdl

Then those four with 'install'

No problems till as far as I can see - no error messages - so I suspect
all is installed completely in /usr and friends.

How are you running the setup.py. Like the docs say:
python2.3 setup.py .... ?
If so you must run with python2.4

I have only one python installed, which is the one that returned 2.4.1,
as I reported before, so I thought it would be sufficient to call python
alone. Anyway, I tried with python2.4 too - same result.

John

···

On Sun, 14 Aug 2005 19:49:36 +0100 Ricardo Pedroso <ricardo.pedroso@netvisao.pt> wrote:

Ok - That worked! I'd like to suggest the following:

In BUILD.txt:

" If you would like to do a Unicode enabled build (all strings sent
   to or retruned from wx functions are Unicode objects) and your
   wxWidgets was built with unicode enabled then add this flag::
                                                                
         UNICODE=1
"

Apparently this option is NOT optional, as it causes all the problems I
had. Wouldn't it be logical to propagate the --enable-unicode to setup.py
(adding the UNICODE=1 automatically)? Maybe the same for the install to
site-packages?

Thanks for the help!

John

···

On Sun, 14 Aug 2005 20:27:32 +0100 Ricardo Pedroso <ricardo.pedroso@netvisao.pt> wrote:

Yes, just python is OK.

Since you build the wxWidgets with unicode, did you have UNICODE = 1 in
you wxPython/config.py or passing UNICODE=1 to setup.py?