[Fwd: Re: [Thuban-list] Module sqlite.py]

[Dan Putler]

Hi Jonathan,

It turns out that the RPMs Robin Dunn is create a private copy of wxGTK 
that lives in /usr/lib/wxPython/lib for wxPython.  His argument for 
doing this is to minimize potential conflicts with other wxWindows 
applications.  He actually provides two sets of build instructions for 
*nix systems.  The following the instructions contained in the file 
README.1st.txt creates a private copy of wxGTK (like the RPMs), and 
following the instructions contained in BUILD.unix.txt results in the 
traditional build of wxPython that you are running.  I followed the 
"new" build instructions (those in README.1st.txt).  However, once I 
followed your instructions concerning various paths (contained in the 
email below), and then rebuilt Thuban, everything was fine.

Thanks for your help.

Dan

Jonathan Coles wrote:
> Dan,
> 
> Having libwx_gtkd-2.4.so in /usr/lib/wxPython/lib seems unusual (I have
> it directly in /usr/lib). Have you compiled wxWindows/wxPython yourself?
> If so, a problem relating back to the original post is whether or not
> you used the same compiler to compile wxWindows/wxPython and Thuban.
> They need to be (roughly) the same. 
> 
> If you didn't compile the libraries, then you'll need to add
> /usr/lib/wxPython/lib to your library path environment variable which
> should be LD_LIBRARY_PATH.
> 
> Also, you really shouldn't need to edit setup.py. It is assumed that
> wx-config is in your command path. You should probably add the path to
> wx-config to your system path.
> 
> It does sound like we're getting closer to a solution.
> 
> btw, could you please CC: your responses to me to the thuban-list. That
> way we have a history of our discussion. thanks.
> 
> --jonathan
> 
> On Fri, 2003-05-02 at 18:21, Dan Putler wrote:
> 
>>Hi Jonathan,
>>
>>The plot thickens, but a solution seems near.
>>
>>
>>>You can find out which libstdc++ library wxproj will use by doing
> 
> the
> 
>>>following from your thuban directory:
>>>
>>>cd Lib
>>>ldd wxproj.so
>>>
>>>This will give a list of the libraries wxproj.so will need. If you
> 
> look
> 
>>>through the list you should find a library that begins with
> 
> libstdc++.
> 
>>>Is it pointing to the correct path? (probably
>>>/usr/lib/gcc-lib/i386-redhat-linux/3.2.2, as you said)
>>
>>I've done this.  It turns out that wxproj.so doesn't want libstdc++ 
>>directly.  It want libproj.so.0, libwx_gtkd-2.4.so, libc.so.6, and 
>>libm.so.6.  It can find everything except libwx_gtkd-2.4.so.  On my 
>>system this module lives in /usr/lib/wxPython/lib.  This seems
> 
> directly 
> 
>>related to the inability of Thuban to find wx_config.  Specifically, 
>>Thuban doesn't seems to be looking for wxPython in /usr/lib/wxPython, 
>>which seems surprising.  Do I need to include /usr/lib/wxPython in my 
>>path?  I've been through setup.py and the only places I can find a
> 
> hard 
> 
>>coded path to wxPython appears to be related to code designed to 
>>generate rpms (or that is my guess based on the variable names).
>>
>>Dan


-- 
_________________________________________
Dan Putler
UBC Commerce
Email: putler at commerce dot ubc dot ca
Phone: 604-822-8329