From: Eric Wong <e@80x24.org>
To: misc@80x24.org
Subject: ./configure --prefix=... for autotooled projects
Date: Sun, 19 Apr 2015 22:39:24 +0000 [thread overview]
Message-ID: <configure-prefix-for-autotooled-projects@20150419> (raw)
autoconf (and any build systems emulating the "./configure" build script)
support a nice --prefix= switch which allows you to install the software
to an easily writable section of your filesystem.
No need for containers, chroots, root access, or weird, package-specific
build/packaging scripts such as RVM (Ruby Version Manager). Just set
PATH and LD_LIBRARY_PATH appropriately.
I can still link to system libraries provided by my GNU/Linux distro, or
I can pass additional arguments and use LD_LIBRARY_PATH/-Wl,-rpath as
necessary to point linkage to newer development versions as needed.
I do this for each project I want the latest revisions of and leave any
distribution-supplied installations untouched.
Sometimes I'll even configure the prefix to be /tmp/$SOMETHING if I
don't care about using something past a reboot :)
Fwiw, GNU/Linux distribution maintainers are likely to set --prefix=/usr
whereas the default is --prefix=/usr/local
And even non-autotooled build systems such as the default GNU Make-based
build system in git supports it. Heck, git was probably the first
project I encountered to default the prefix to $HOME instead of
/usr/local
reply other threads:[~2015-04-19 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=configure-prefix-for-autotooled-projects@20150419 \
--to=e@80x24.org \
--cc=misc@80x24.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).