[Zlib-devel] CHOST option

[Enrico Weigelt]

* Volker Grabsch <vog at notjusthosting.com> schrieb:

> > This only works in the specific case that you have only *one*
> > toolchain per target-tuple and its commands are available
> > under these names.
> 
> That is by far the most common case, so providing a handy
> shortcut for that case is a very sensible thing to do.

Maybe in number of performed builds, but not technically.
BTW: that approach *only* works if you have only one toolchain
per target-tuple, otherwise you'll easily get into big trouble.

> However, in that case the first approach ("make CROSS=i686-pc-mingw32-")
> would still work, wouldn't it?
> 
>     make CROSS=/path/to/toolchain/bin/
> or:
>     make CROSS=/path/to/toolchain/bin/i686-xx-yyy-
> 
> And in the end, zlib's CROSS_PREFIX is exactly that, isn't it?

I'll first have to check it carefully to answer this. My build 
machinery passes individual toolchain commands - for almost a
decade now - as this is the de facto standard. (for those who
don't, I mainain my own branch).

For me it is vital that this approach works reliably. If there's
an additional way, I'm fine w/ it, as long as it clearly does
NOT conflict w/ the tradional one whatsoever.

cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------