From: Joshua Watt <jpewhacker@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>, Stefan Agner <stefan@agner.ch>
Cc: Stefan Agner <stefan.agner@toradex.com>,
Otavio Salvador <otavio@ossystems.com.br>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] waf.bbclass: explicitly pass libdir
Date: Mon, 11 Dec 2017 09:32:18 -0600 [thread overview]
Message-ID: <1513006338.9676.5.camel@gmail.com> (raw)
In-Reply-To: <CAJTo0LY5BR=kgukiW6LAjonzidsC-h0gerwxKcA-3Qqvydniuw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3154 bytes --]
On Mon, 2017-12-11 at 14:58 +0000, Burton, Ross wrote:
> On 11 December 2017 at 14:16, Stefan Agner <stefan@agner.ch> wrote:
> > Hm, isn't this a "base" option which is always supported?
>
> No idea. :)
>
> > There are a bunch of others. But most seem to derive from PREFIX,
> > which
> >
> > we set...
> >
> >
> >
> > Installation prefix:
> >
> >
> >
> > By default, "waf install" will put the files in
> > "/usr/local/bin",
> >
> > "/usr/local/lib" etc. An installation prefix other than
> >
> > "/usr/local" can be given using "--prefix", for example
> >
> > "--prefix=$HOME"
> >
> >
> >
> >
> >
> >
> >
> > --prefix=PREFIX installation prefix [default:
> > '/usr/local/']
> >
> > --destdir=DESTDIR installation root [default: '']
> >
> > --exec-prefix=EXEC_PREFIX
> >
> > installation prefix for binaries [PREFIX]
> >
> >
> >
> > Installation directories:
> >
> > --bindir=BINDIR user commands [EXEC_PREFIX/bin]
> >
> > --sbindir=SBINDIR system binaries [EXEC_PREFIX/sbin]
> >
> > --libexecdir=LIBEXECDIR
> >
> > program-specific binaries
> > [EXEC_PREFIX/libexec]
> >
> >
> >
> > --sysconfdir=SYSCONFDIR
> >
> > host-specific configuration [PREFIX/etc]
> >
> > --sharedstatedir=SHAREDSTATEDIR
> >
> > architecture-independent variable data
> >
> > [PREFIX/com]
> >
> >
> >
> > --localstatedir=LOCALSTATEDIR
> >
> > variable data [PREFIX/var]
> >
> > --libdir=LIBDIR object code libraries [EXEC_PREFIX/lib64]
> >
> > --includedir=INCLUDEDIR
> >
> > header files [PREFIX/include]
> >
> > --oldincludedir=OLDINCLUDEDIR
> >
> > header files for non-GCC compilers
> >
> > [/usr/include]
> >
> >
> >
> > --datarootdir=DATAROOTDIR
> >
> > architecture-independent data root
> >
> > [PREFIX/share]
> >
> >
> >
> > --datadir=DATADIR architecture-independent data [DATAROOTDIR]
> >
> > --infodir=INFODIR GNU "info" documentation [DATAROOTDIR/info]
> >
> > --localedir=LOCALEDIR
> >
> > locale-dependent data [DATAROOTDIR/locale]
> >
> > --mandir=MANDIR manual pages [DATAROOTDIR/man]
> >
> > --docdir=DOCDIR documentation root
> > [DATAROOTDIR/doc/PACKAGE]
> >
> > --htmldir=HTMLDIR HTML documentation [DOCDIR]
> >
> > --dvidir=DVIDIR DVI documentation [DOCDIR]
> >
> > --pdfdir=PDFDIR PDF documentation [DOCDIR]
> >
> > --psdir=PSDIR PostScript documentation [DOCDIR]
>
> But we do allow distros to override those, so passing the on
Vanilla waf only supports --prefix, --libdir, and --bindir. Anything
else is a result of loading the gnu_dirs tool, which not all projects
are required to do.
> es that we can is good. bitbake.conf has the canonical list of
> prefix variables that we expose.
>
> Ross
>
[-- Attachment #2: Type: text/html, Size: 4648 bytes --]
next prev parent reply other threads:[~2017-12-11 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 13:57 [PATCH] waf.bbclass: explicitly pass libdir Stefan Agner
2017-12-11 14:01 ` Burton, Ross
2017-12-11 14:16 ` Stefan Agner
2017-12-11 14:58 ` Burton, Ross
2017-12-11 15:32 ` Joshua Watt [this message]
2017-12-11 15:37 ` Joshua Watt
2017-12-11 17:09 ` Burton, Ross
2017-12-11 17:15 ` Otavio Salvador
2017-12-12 7:48 ` Stefan Agner
2017-12-12 10:58 ` Burton, Ross
2017-12-12 11:07 ` Stefan Agner
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=1513006338.9676.5.camel@gmail.com \
--to=jpewhacker@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=ross.burton@intel.com \
--cc=stefan.agner@toradex.com \
--cc=stefan@agner.ch \
/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