While technically correct I strongly suggest against using absolute paths into your home directory like that. I would recommend instead using $$(PWD) as the base for a path (for instance, $$(PWD)/../mylib/) so that other people can build your project and still have it work.
/s/ Adam On Wed, Dec 23, 2009 at 1:32 PM, Marc Durant <mdur...@txcorp.com> wrote: > You'll need to add an "rpath" option in your .pro file. Here's an > example from one of my projects where I give the library directory for > python, the rpath directory, and then the library itself. The > directory named by rpath tells the executable where to look for this > particular library. > > LIBS += -L/home/mdurant/Source/visit2_svn/visit/python/2.5/linux- > x86_64_gcc-4.3.0/lib/python2.5/config \ > -Wl,-rpath,/home/mdurant/Source/visit2_svn/visit2.0.0/ > python/2.5/linux-x86_64_gcc-4.3.0/lib/python2.5/config \ > -lpython2.5 > > -marc > > On Dec 23, 2009, at 12:16 PM, Ed Sutton wrote: > >> When I run the Qt created Makefile to build the client that uses my >> shared library, I get the following warning: >> >> /mylib.so, not found (try using -rpath or -rpath-link) >> >> Can someone please provide and example of what to add to the QT >> project file to generate a happy Makefile? >> >> It builds fine from within QT Creator after I had set the build >> environment LD_LIBRARY_PATH to include the shared library path. >> >> Thanks in advance, >> >> -Ed >> >> >> _______________________________________________ >> Qt-creator mailing list >> Qt-creator@trolltech.com >> http://lists.trolltech.com/mailman/listinfo/qt-creator > > _______________________________________________ > Qt-creator mailing list > Qt-creator@trolltech.com > http://lists.trolltech.com/mailman/listinfo/qt-creator > _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
