Remember me

Lost Password?

Register now!


Who's Online
54 user(s) are online (41 user(s) are browsing Forums)

Members: 0
Guests: 54


Support us!


Report message:*

Re: Building Cross-Compiling adtools for Amiga OS4 PowerPC (ppc) with Cygwin/Bash on Ubuntu on Windows

Subject: Re: Building Cross-Compiling adtools for Amiga OS4 PowerPC (ppc) with Cygwin/Bash on Ubuntu on Windows
by broadblues on 2017/11/8 23:21:00


Well, you're more experienced than me in this stuff...

That said, someone really needs to clarify the terminology and make sure that configure scripts stick to it. Because even what you said doesn't match the document you linked to 100%, which says:

Mick is wrong in this case, no disrespect intended, he tends to build libraries and apps where 'host' and 'target' are effectively the same thing. For a cross compiler they aren't, as that's actually the whole point.


the machine you are building on (build), the machine that you are building for (host), and the machine that GCC will produce code for (target)

If you are building a cross compiler for amigaos the target will stay fixed as ppc-amigaos,

I'd say the build and host would usually be the same, unless you are attempting to cross compile the cross compiler!!!


Specifying the host without specifying the build should be avoided, as configure may (and once did) assume that the host you specify is also the build, which may not be true.

It may not be true but would be a common case for build a cross compiler on the machine you intend to cross compile on.

NB I haven't read the thread as a whole and the title does suggest this may be one case where all three are different...


I've seen conflicting examples too. SOme use --target, others --host, and some set all three including this one for SDL2.

There is no conflict there, SDL2 is library so it's host and target will always be the same and so the meaning of build, host and target in the above description are completely consistant with the example at the link you gave.

Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project