Re: Cross-compilation

[Ladislav Michl]

On Fri, Jan 10, 2020 at 03:46:47PM +0100, Ladislav Michl wrote:
> Hi Frederik,
> 
> On Fri, Jan 10, 2020 at 02:59:03PM +0100, Frederik Seiffert wrote:
> > Hi Ladislav,
> > 
> > You might want to have a look at the scripts of the GNUstep Android 
> > toolchain project, which cross-compiles GNUstep for Android:
> > http://github.com/gnustep/tools-android
> 
> This one I already evaluated, it sets --host even on gnustep-make
> package, but this package is not target, but cross one.

...and it works only because all used tools are set in environment in
env/toolchain.sh.
 
> > Hope that helps, and let me know if you have any questions.
> 
> Yes, those I already asked :) In case even gnustep-make is target package,
> I can live with that, but then I need to hack my cross build enviroment
> to accept this exception, just because it is ... exception. I'm not aware
> any other package being setup this way.

Well, tools-android project is pretty misleading example and setting
--host=${ANDROID_TARGET} in phases/20-gnustep-make.sh is just wrong.

gnustep-make itself is a (cross)tool package, it does evaluate compile
tools and makes decision based on that. Obviously, it cannot do that
for tools running on host. See autoconf manual for more:
https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html

As section '1.2.5 Configuring for a cross-compile target' of
gnustep-make/INSTALL is already there, let's fix configure script
to follow it.

Unfortunately, configure.ac was cultivated to meet various needs
as they showed up, so it is not easy to fix without breaking anyone's
setup. I'll sent patches to test in separate thread.

Best regards,
        ladis