<html><head></head><body><div>On Mon, 2017-12-11 at 09:32 -0600, Joshua Watt wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div>On Mon, 2017-12-11 at 14:58 +0000, Burton, Ross wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr">On 11 December 2017 at 14:16, Stefan Agner <span dir="ltr"><<a href="mailto:stefan@agner.ch" target="_blank">stefan@agner.ch</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">Hm, isn't this a "base" option which is always supported?<br></blockquote><div><br></div><div>No idea. :)</div><div> </div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex">There are a bunch of others. But most seem to derive from PREFIX, which<br>
we set...<br>
<br>
Installation prefix:<br>
<br>
By default, "waf install" will put the files in "/usr/local/bin",<br>
"/usr/local/lib" etc. An installation prefix other than<br>
"/usr/local" can be given using "--prefix", for example<br>
"--prefix=$HOME"<br>
<br>
<br>
<br>
--prefix=PREFIX installation prefix [default: '/usr/local/']<br>
--destdir=DESTDIR installation root [default: '']<br>
--exec-prefix=EXEC_PREFIX<br>
installation prefix for binaries [PREFIX]<br>
<br>
Installation directories:<br>
--bindir=BINDIR user commands [EXEC_PREFIX/bin]<br>
--sbindir=SBINDIR system binaries [EXEC_PREFIX/sbin]<br>
--libexecdir=LIBEXECDIR<br>
program-specific binaries [EXEC_PREFIX/libexec]<br>
<br>
--sysconfdir=SYSCONFDIR<br>
host-specific configuration [PREFIX/etc]<br>
--sharedstatedir=<wbr>SHAREDSTATEDIR<br>
architecture-independent variable data<br>
[PREFIX/com]<br>
<br>
--localstatedir=LOCALSTATEDIR<br>
variable data [PREFIX/var]<br>
--libdir=LIBDIR object code libraries [EXEC_PREFIX/lib64]<br>
--includedir=INCLUDEDIR<br>
header files [PREFIX/include]<br>
--oldincludedir=OLDINCLUDEDIR<br>
header files for non-GCC compilers<br>
[/usr/include]<br>
<br>
--datarootdir=DATAROOTDIR<br>
architecture-independent data root<br>
[PREFIX/share]<br>
<br>
--datadir=DATADIR architecture-independent data [DATAROOTDIR]<br>
--infodir=INFODIR GNU "info" documentation [DATAROOTDIR/info]<br>
--localedir=LOCALEDIR<br>
locale-dependent data [DATAROOTDIR/locale]<br>
--mandir=MANDIR manual pages [DATAROOTDIR/man]<br>
--docdir=DOCDIR documentation root [DATAROOTDIR/doc/PACKAGE]<br>
--htmldir=HTMLDIR HTML documentation [DOCDIR]<br>
--dvidir=DVIDIR DVI documentation [DOCDIR]<br>
--pdfdir=PDFDIR PDF documentation [DOCDIR]<br>
--psdir=PSDIR PostScript documentation [DOCDIR]<br></blockquote><div><br></div><div>But we do allow distros to override those, so passing the on</div></div></div></div></blockquote><div><br></div><div>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.</div></blockquote><div><br></div><div>Sorry, hit send too soo: waf (at least version 2.0) also errors out on unknown options. I think the three I listed are the only ones we can do generically. There might be some way to easily adding the rest if you know waf is loading gnu_dirs</div><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div><br></div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>es that we can is good. bitbake.conf has the canonical list of prefix variables that we expose.</div><div><br></div><div>Ross <br></div></div></div></div>
</blockquote></blockquote></body></html>