On 4/3/08, Bob Rossi <[EMAIL PROTECTED]> wrote: > On Thu, Apr 03, 2008 at 08:36:44AM -0600, John Calcote wrote: > > Bob, > >> On linux, there is no such guarentee. So, I have come up with 2 > >> solutions, and wonder if someone else has a better idea, or prefers one > >> over the others. > >> > >> - Modify the automake to build the program as foo-bin, instead of foo > >> on unix platforms. Then, install a script called foo, that sets the > >> LD_LIBRARY_PATH and invokes foo-bin. > >> This approach seems like a lot of modification to the autotools in > >> order to get the tool to build with both static and dynamic version > >> of wxwidgets. > >> > >> - Modify foo to know if it is using a shared wxwidgets library, and > >> dlopen it if it is. I haven't tested this yet, and don't even know > >> if it will work. > > I recommend you put the library in the bin directory on mingw and in the > > lib directory on other platforms. This is proper for both systems. What it > > requires is an conditional section in your Makefile.am, checking for mingw > > platform. The variable can be setup in your configure.ac script, and > > exported using AM_CONDITIONAL. > > If I put it in the lib directory on other platforms, on startup, how > will the binary know where to find the .so? That's why I was asking > about LD_LIBRARY_PATH, and creating a script....
If it's in the lib directory on non-unix systems, I don't think you need to set LD_LIBRARY_PATH. Similarly, if it's in the bin directory on Windows, you're ok, too.