Ugh, I hate that "seems to work" it indicates a lack of knowledge on how
libraries are handled, which can come back to burn you.
ls.so.conf file is key to "seems to work" same as the ldconfig command, and
LD_LIBRARY_PATH environment variable.
You'll also find problems with plugins (especially the image ones) knowing the
command 'ldd' woudl be of great benefit.
My advice is stick to 'make bindist' because it has been written by people much
more familiar with packaging in general and Qt packaging in specific. If you
don't use bindist, at least take a look at what it does.
________________________________
From: Duane <[email protected]>
To: [email protected]
Sent: Thursday, July 19, 2012 10:17 AM
Subject: Re: [Qt-creator] lib search path
On 07/19/2012 07:42 AM, [email protected] wrote:
>
> On 19 Jul 2012, at 13:00, ext Diego Iastrubni wrote:
>
>>
>> On Thu, Jul 19, 2012 at 1:50 PM, Duane Hebert <[email protected]>
>> wrote:
>> I installed Qt from the SDK. It works fine on my desktop. But when I
>> install my application on our target controller, it doesn't find them unless
>> I put them in /usr/lib.
>> BTW I would just do this but one of our guys says that libs should be in
>> usr/local/lib. Is there any reason for this?
>>
>>
>> If you deploy the QtLibs with your application into a non standard lib you
>> might want to wrap your binary with a shell script which set LD_LIBRARY_PATH.
>>
>> You might also read these docs:
>> http://qt-project.org/doc/qt-4.8/deployment.html
>
> You can also just run "make bindist" in the qt creator build. That creates a
> deployable bundle that includes the Qt that you used to compile Qt Creator.
>
Thanks for all of the suggestions. We decided to just deploy the Qt
libs in usr/lib. This seems to work.
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator
