Hi,

From time to time, we use UDBCSQLite for our workshops and interactive documentation examples and is a pretty good project for bridging the Smalltalk world and the relational database world.

A common glitch is locating the binary of sqlite3 for 32 bits and putting it in a place that is available for the VM. I just make this small hack:

===

UDBCSQLite3Library>>#library

    Smalltalk os isMacOS ifTrue: [ ^ #sqlite3 ].
    Smalltalk os isUnix ifTrue: [ ^ '/usr/lib32/libsqlite3.so'].
    ^'sqlite3'

===

and now is working pretty well on my machine. Of course, this only works on Arch 64 bits and its derivates and could change in other Gnu/Linux variants. So, I'm wondering for a better way to make the path to the sqlite binary not hard coded into UDBCSQLite3 and creating some #library: setter that lets the user to setup the sqlite3 location if the file on UDBCSQLite3Library>>#library is non-existent or wrong.

I'm sending this to the list, because AFAIK there is no ticketing on STHub to discuss code issues.

Cheers,

Offray



Reply via email to