From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Important instructions to manually compile kde apps
Date: Sun, 25 Nov 2001 22:07:35 +0200 [thread overview]
Message-ID: <0GND00K6KH6Q8X@mxout2.netvision.net.il> (raw)
Hi all,
Right now, with the "multi-kdelibs scheme", to compile a KDE app you need to
do:
---
export KDEDIR=/usr/lib/kdelibs-$ver
./configure --prefix=/usr[/local]
---
(/usr/local being recommended for manually compiled apps)
Also, kdevelop requires a correct KDEDIR setting (like the one above) to run
configure scripts.
I want to put this KDEDIR setting into /etc/env.d. This may cause people who
don't read the above instructions to run configure without parameters, and
their app will then install into KDEDIR=/usr/lib/kdelibs-* which is bad. They
won't be expecting that because /usr/local is the default, but KDEDIR
overrides it in this case.
So, this needs to be put somewhere where many people will see it - a FAQ item
probably, but most people don't read the FAQs until they have a problem.
Suggestions? Where should this go?
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next reply other threads:[~2001-11-25 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 20:07 Dan Armak [this message]
2001-11-25 20:37 ` [gentoo-dev] Important instructions to manually compile kde apps Collins Richey
2001-11-25 20:41 ` Collins Richey
2001-11-26 8:44 ` Geert Bevin
2001-11-26 16:10 ` Bart Verwilst
2001-11-26 23:52 ` Geert Bevin
2001-11-27 6:08 ` Dan Armak
2001-11-27 15:54 ` [gentoo-dev] reiserfs version? nrb23
2001-11-27 16:06 ` djamil essaissi
2001-11-27 16:08 ` nrb23
2001-11-27 16:17 ` djamil essaissi
2001-11-27 22:26 ` [gentoo-dev] Important instructions to manually compile kde apps Geert Bevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0GND00K6KH6Q8X@mxout2.netvision.net.il \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox