Re: Mac osx 10.4.9 ppc build from svn source, APSW issues

Tim,
Thanks to you, I finally have Bitpim running from svn source. My  
Python is 2.5, wxPython 2.8.3-unicode, sqlite-3.3.15 from a new  
source package, and APSW from svn sources version 396.
I followed your instruction for the sqlite3 build, and I also used  
the APSW instructions from:
http://initd.org/pub/software/pysqlite/apsw/3.3.13-r1/apsw.html
I followed their guidance for adding a sqlite3 subdir in APSW, I  
think that this is supposed to include sqlite3 in APSW. That still  
didn't work so I used your "export DYLD_LIBRARY_PATH=/usr/local/lib"  
line.
The APSW install with the sqlite3 subdir probably does nothing,  like  
you said library path seems to be the key here.
Now I can finally look into those new phone files.

Dave

On Apr 10, 2007, at 12:48 PM, T Gallagher wrote:

> David,
>
> I had the same errors before and they were resolved when I followed  
> along with the
> procedure shown below.  Seems the trick was to add the shared  
> library path.
>
> Tim
>
> Quote ==============================
> ===================
> Ok, I finally got BitPim running on Intel 10.4.9 with Python 2.5 and
> wxPython 2.8.1.1.
>
> Here's what I did:
>
> First as Sean suggested, I rebuilt sqlite3. Now part of that is
> actually installing it (via sudo make install), not only using it as
> part of the shared library when compiling apsw. This will place a
> copy of sqlite 3.3.13 into /usr/local/lib.
>
> I also installed apsw by following the directions in its  
> documentation.
>
> Since I am using tcsh as my shell, I use setenv to export my
> environment variables like:
>
> setenv DYLD_LIBRARY_PATH /usr/local/lib
>
> For bash it would be:
>
> export DYLD_LIBRARY_PATH=/usr/local
> /lib
>
> After setting the variable, BitPim would run successfully. However,
> that only works as long as the variable is present, so if you kill
> your terminal session, you'll have to export it again.
>
> When I ran BitPim months ago with a previous version of apsw, I
> thought that sqlite3 was bundled into the .so file once it was
> compiled. Am I incorrect in assuming that is the case now? Why would
> it have to link against a version at run time now? Maybe the version
> of apsw at that time was compatible with the version of sqlite3
> installed on Tiger by default so I never saw that error.
>
> These are where I got the versions of Python and wxPython from:
>
> - Python 2.5 from python.org
> -  wxPython 2.8.11 from http://www.wxpython.org/download.php and used
> the wxpython osx-unicode-py2.5 link.
>
> I have yet to try making a build, but that will be the next step. I
> also checked my version of apsw.so and it is universal.
>
> Hope this helps anyone out needing to run from source.
>
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV