[aur-general] Conventions on packages for cross-compiling

[Allan McRae]

Vojtech Horky wrote:
> 2009/10/15 Allan McRae <allan at archlinux.org>:
>   
>> Vojtech Horky wrote:
>>     
>>> Hi,
>>> 2009/10/14 Allan McRae <allan at archlinux.org>:
>>>
>>>       
>>>> 3) add symlinks for all ${_sysroot}/bin/${_target}-* to /usr/bin
>>>>
>>>>         
>>> Is there any special reason why not to use directly --bindir=/usr/bin?
>>>
>>>       
>> Um... no reason....   just never thought of that.  I will adjust my packages
>> today to give that a spin but I can not see any reason why that will not
>> work.
>>
>>
>>     
>>> If there aren't any objections to this file placement, will you update
>>> the wiki proposal or shall I do it?
>>>
>>>       
>> Either.  I can make a first pass if you would like.  Writing documentation
>> is not my strong point :)
>>     
> I rewrote it a bit to describe using the /usr/lib/cross-* directory.
> Feel free to update it if something looks too confusing or wrong.
> BTW, I am not very good at writing such things either :).
>   

Great.  I think we can take the discussion to the talk page on the wiki 
to try and keep it all in one place.

>>
>>     
> And one more thing. It is just an idea: shall we create that
> "out-of-path" thing that I wrote about at the end of the wiki?
> [In brief: create symlinks with normal (i.e. without architecture
> prefix) names to the executables and put them into directory outside
> of path. If there are scripts using directly 'gcc', adding this
> directory to $PATH would force their usage when cross-compiling.]
> Any comments/thoughts on this?
>   

I see binutils puts its binaries (without target name) in 
/usr/lib/cross-i686-pc-mingw32/i686-pc-mingw32/bin.  It is a bit of a 
mouthful though...  anyway - discussion on wiki.

Allan