logo       

Re: beginner question regarding config.in syntax: msg#00132

t2.devel

Subject: Re: beginner question regarding config.in syntax



This is a multi-part message in MIME format.
thx. for your fast reply. I have found it in the t2-handbook (chapter 7:
Exceptionl Installation Methods).
I don't know the english version but in german we will say "wer lesen kann ist
klar im Vorteil" ;-).

flo

René Rebe wrote:
>Hi again,
>
>I wrote:
>>> Ok. Here are the last questions:
>>> Is there any way to "export" the root file system to a defined folder
>>> like /media/disk or /mnt? Is it possible to do the same for the
>>> toolchain?
>>>
>>
>> Not yet, but you can just add a cp or rsync at the end of your custom
>> build.sh inside
>> your target directory, such as target/.../build.sh
>>
>> We could also add something like this to the provided output
>> post-processing if
>> useful for more people.
>>
>> Note that the T2 cross toolchain is not relocatable, that means it is
>> only functional
>> if started from the location it was build, such as
>> /home/some-user/src/t2-trunk/.
>> This is due to hardcoded paths in the compiler, linker et al. If other
>> system
>> providers have patches for this to replace the system-root with some
>> environment
>> variable this could be easily fixable, just that noone needed this in
>> T2 so far to
>> really look into it.
>PS: May be be as simple as automatically injecting --sysroot=$root, or
>similar.
>
>--
> René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
> http://exactcode.de | http://t2-project.org | http://rene.rebe.name



<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise