On Wed, Mar 11, 2015 at 7:59 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On Wednesday 11 March 2015 23:50:52 Nikos Chantziaras wrote:
On 10/03/15 21:07, Scott Aron Bloom wrote:
When building Qt for distribution via LGPL of a closed source product
using shared libraries.
On Tuesday 14 April 2015 12:37:32 Mike Jackson wrote:
For reference, if you want to use RPATH instead of RUNPATH, use:
-Wl,-rpath=\$ORIGIN/lib,--disable-new-dtags
Note: it is somewhat of a nightmare to escape the $ in \$ORIGIN in a
way that can make it undamaged to the final
On 11/03/15 22:52, Michael Jackson wrote:
So if i have my executable in [install]/bin and libQt5Core.so.5 in
[install]/lib then I should be able to just generate a package by copying the
Qt libraries from the Qt 5.4.1 installation location. I am used to stuff like
this on OS X where I have
On Mar 11, 2015, at 9:54 AM, Koehne Kai kai.koe...@theqtcompany.com wrote:
-Original Message-
From: interest-bounces+kai.koehne=theqtcompany@qt-project.org
[...]
The usual approach on unix based systems is to ship a script that runs
the executable with the proper library path
On 11/03/15 23:31, Nikos Chantziaras wrote:
On 11/03/15 22:52, Michael Jackson wrote:
So if i have my executable in [install]/bin and libQt5Core.so.5 in
[install]/lib then I should be able to just generate a package by copying
the Qt libraries from the Qt 5.4.1 installation location. I am
On 10/03/15 21:07, Scott Aron Bloom wrote:
When building Qt for distribution via LGPL of a closed source product
using shared libraries.
What is the best method to make sure the plugins pickup the Qt libraries
you are shipping?
As Thiago mentioned, you can use RPATH. However, RPATH is
On 11/03/15 23:50, Nikos Chantziaras wrote:
[...]
To do that, link with:
-Wl,-rpath=\$ORIGIN/lib,--enable-new-dtags
This will look in the lib subdirectory first for libraries and only
consider default locations if a library is not found in lib. So if you
install your main binary in:
On Wednesday 11 March 2015 23:50:52 Nikos Chantziaras wrote:
On 10/03/15 21:07, Scott Aron Bloom wrote:
When building Qt for distribution via LGPL of a closed source product
using shared libraries.
What is the best method to make sure the plugins pickup the Qt libraries
you are
Den 10-03-2015 kl. 20:07 skrev Scott Aron Bloom:
When building Qt for distribution via LGPL of a closed source product
using shared libraries.
What is the best method to make sure the plugins pickup the Qt
libraries you are shipping?
In this case you mean this as a help to the user,
On Mar 11, 2015, at 5:56 AM, Bo Thorsen b...@vikingsoft.eu wrote:
Den 10-03-2015 kl. 20:07 skrev Scott Aron Bloom:
When building Qt for distribution via LGPL of a closed source product
using shared libraries.
What is the best method to make sure the plugins pickup the Qt
libraries you
-Original Message-
From: interest-bounces+kai.koehne=theqtcompany@qt-project.org
[...]
The usual approach on unix based systems is to ship a script that runs
the executable with the proper library path set. This way you can
support multiple install locations which rpath can't
On Tuesday 10 March 2015 19:07:19 Scott Aron Bloom wrote:
When building Qt for distribution via LGPL of a closed source product using
shared libraries.
What is the best method to make sure the plugins pickup the Qt libraries you
are shipping?
RPATH with $ORIGIN and make sure that the linker
When building Qt for distribution via LGPL of a closed source product using
shared libraries.
What is the best method to make sure the plugins pickup the Qt libraries you
are shipping?
Scott
___
Interest mailing list
Interest@qt-project.org
13 matches
Mail list logo
