Cross Compiling: Difference between revisions

imported>Danbst
lazy cross compiling
imported>Jtojnar
m do not use pkgconfig alias
Line 106: Line 106:
** compiler producing native binaries go to <code>depsBuildBuild</code>
** compiler producing native binaries go to <code>depsBuildBuild</code>
** compiler producing cross binaries, all setup hooks and programs executed by the builder go to <code>depsBuildHost</code>
** compiler producing cross binaries, all setup hooks and programs executed by the builder go to <code>depsBuildHost</code>
*** common examples: <code>pkgconfig, autoreconfHook, makeWrapper, intltool, bison, flex</code>
*** common examples: <code>pkg-config, autoreconfHook, makeWrapper, intltool, bison, flex</code>
* If it is used at run-time it's <code>depsHostXXX</code>. [Stack linking doesn't effect this, even if it allows us to forget where things came from.]
* If it is used at run-time it's <code>depsHostXXX</code>. [Stack linking doesn't effect this, even if it allows us to forget where things came from.]
** if it’s an interpreter that will be needed by an installed script, it should go in <code>depsHostTarget</code>.  
** if it’s an interpreter that will be needed by an installed script, it should go in <code>depsHostTarget</code>.