When I build tqt3 from GIT, the pkgconfig file gets built and installed to:
/opt/trinity/lib/tqt3-R14.0.0/lib/pkgconfig/tqt-mt.pc
rather than
/opt/trinity/lib/pkgconfig/tqt-mt.pc
Bug?
Darrell
When I build tqt3 from GIT, the
pkgconfig file gets built and installed
to:
/opt/trinity/lib/tqt3-R14.0.0/lib/pkgconfig/tqt-mt.pc
rather than
/opt/trinity/lib/pkgconfig/tqt-mt.pc
Bug?
Most probably. That path looks nasty.
Fixable from here or do we need a bug report?
Darrell
When I build tqt3 from GIT, the
pkgconfig file gets built and installed
to:
/opt/trinity/lib/tqt3-R14.0.0/lib/pkgconfig/tqt-mt.pc
rather than
/opt/trinity/lib/pkgconfig/tqt-mt.pc
Bug?
Most probably. That path looks nasty.
Fixable from here or do we need a bug report?
Bug report is a good idea. I'm going to be swamped at my day job real quick, so it may have to wait until someone else patches it.
Tim
/opt/trinity/lib/tqt3-R14.0.0/lib/pkgconfig/tqt-mt.pc
rather than
/opt/trinity/lib/pkgconfig/tqt-mt.pc
Bug?
Most probably. That path looks nasty.
Fixable from here or do we need a bug report?
Bug report is a good idea. I'm going to be swamped at my day job real quick, so it may have to wait until someone else patches it.
Can you provide me soe clues? I don't mind taking a wack.
Darrell
Bug report is a good idea. I'm going to be
swamped at
my day job real quick, so it may have to wait until someone else
patches
it.
Can you provide me so[m]e clues? I don't mind taking a wack.
The problem is in the qt3 code. I never paid attention before, but there is a snippet in the original qt3 build script from Slackware that fixes the problem:
# Make a link to qt-mt.pc mkdir -p $PKG${PREFIX}/lib${LIBDIRSUFFIX}/pkgconfig cd $PKG${PREFIX}/lib${LIBDIRSUFFIX}/pkgconfig ln -sf ../$PRGNAM-$VERSION/lib/pkgconfig/qt-mt.pc . cd -
Bug report 796 filed.
Darrell
On Sunday 15 January 2012 11:25:10 pm Darrell Anderson wrote:
When I build tqt3 from GIT, the
pkgconfig file gets built and installed
to:
/opt/trinity/lib/tqt3-R14.0.0/lib/pkgconfig/tqt-mt.pc
rather than
/opt/trinity/lib/pkgconfig/tqt-mt.pc
Bug?
Most probably. That path looks nasty.
Fixable from here or do we need a bug report?
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
It is the reason I choose to build trinity to belong in /usr as I don't have to move many files to their proper places.
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
Are you saying that when I create Trinity packages to install to /opt/trinity, I should still install pkgconfig files to /usr/lib/pkgconfig?
It is the reason I choose to build trinity to belong in /usr as I don't have to move many files to their proper places.
I can do that for myself, but not when I am packaging for other people who are using the same stock distro, which expects KDE4 to be installed in /usr. :(
Darrell
On Monday 16 January 2012 08:50:34 am Darrell Anderson wrote:
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
Are you saying that when I create Trinity packages to install to /opt/trinity, I should still install pkgconfig files to /usr/lib/pkgconfig?
Yes that is correct. pkg-config looks there by default as that is how the default configuruation is. I ove all of the ones that are not installed there. Less toruble that way.
It is the reason I choose to build trinity to belong in /usr as I don't have to move many files to their proper places.
I can do that for myself, but not when I am packaging for other people who are using the same stock distro, which expects KDE4 to be installed in /usr. :(
I have not looked at that as I don't do KDE4. I will look at that in the future after I get my LFS build completed. I am moving from Arch Linux to LFS. Arch linux just isn't for me anymore, I don't like the direction they are going.
Baho Utot wrote:
On Monday 16 January 2012 08:50:34 am Darrell Anderson wrote:
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
Are you saying that when I create Trinity packages to install to /opt/trinity, I should still install pkgconfig files to /usr/lib/pkgconfig?
Yes that is correct. pkg-config looks there by default as that is how the default configuruation is. I ove all of the ones that are not installed there. Less toruble that way.
There is nothing wrong with putting a group of .pc files in another location, say, /opt/trinity/lib/pkgconfig. You only have to set one environment variable:
PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:/opt/xorg/lib/pkgconfig
To me, just setting a variable once is far less trouble than moving files for every package. It also supports the situation where you may want to have trinity-3.5.13 and trinity-devel on the same system.
Users who don't build from source don't have to worry about it at all.
-- Bruce
On Monday 16 January 2012 12:00:59 pm Bruce Dubbs wrote:
Baho Utot wrote:
On Monday 16 January 2012 08:50:34 am Darrell Anderson wrote:
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
Are you saying that when I create Trinity packages to install to /opt/trinity, I should still install pkgconfig files to /usr/lib/pkgconfig?
Yes that is correct. pkg-config looks there by default as that is how the default configuruation is. I ove all of the ones that are not installed there. Less toruble that way.
There is nothing wrong with putting a group of .pc files in another location, say, /opt/trinity/lib/pkgconfig. You only have to set one environment variable:
PKG_CONFIG_PATH=/opt/trinity/lib/pkgconfig:/opt/xorg/lib/pkgconfig
To me, just setting a variable once is far less trouble than moving files for every package. It also supports the situation where you may want to have trinity-3.5.13 and trinity-devel on the same system.
Users who don't build from source don't have to worry about it at all.
-- Bruce
True
If one either moves the .pc file to /usr/lib/pkgconfig or symlinks in tha package then I don't have to mess around define vars. or things of the nature. "It just works"
On Mon, 16 Jan 2012 05:50:34 -0800 (PST) Darrell Anderson humanreadable@yahoo.com wrote:
As a packager you should move it to /usr/lib/pkgconfig. That's where all the pkcconfig files should be anyway.
Are you saying that when I create Trinity packages to install to /opt/trinity, I should still install pkgconfig files to /usr/lib/pkgconfig?
My .pc files (except tqt.pc IIRC) are in /opt/kde3/lib/pkgconfig, this doesn't cause any problem if PKG_CONFIG_PATH includes /opt/kde3/lib/pkgconfig. It is in my build script.
It is the reason I choose to build trinity to belong in /usr as I don't have to move many files to their proper places.
I can do that for myself, but not when I am packaging for other people who are using the same stock distro, which expects KDE4 to be installed in /usr. :(
Darrell
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
/dev/ammo42 -
Baho Utot -
Bruce Dubbs -
Darrell Anderson -
Timothy Pearson