Am Montag, 1. November 2010, 22:28:32 schrieb Andrew:
> 01.11.2010 22:41, KP Kirchdoerfer пишет:
> >>> Hi Andrew;
> >>>
> >>> ok it starts compiling buildenv.
> >>>
> >>> Do I understand the current process correct, that
> >>> a) a new masterinclude is needed for each arch?
> >>
> >> No, just ad
01.11.2010 22:41, KP Kirchdoerfer пишет:
>
>>> Hi Andrew;
>>>
>>> ok it starts compiling buildenv.
>>>
>>> Do I understand the current process correct, that
>>> a) a new masterinclude is needed for each arch?
>> No, just added arch suffix into masterinclude.mk; and then rebuild all.
> Sorry, I was
Am Montag, 1. November 2010, 21:29:18 schrieb Andrew:
> 01.11.2010 22:07, KP Kirchdoerfer пишет:
> > Am Montag, 1. November 2010, 17:49:33 schrieb Andrew:
> >> 01.11.2010 16:23, KP Kirchdoerfer пишет:
> >>> Am Montag, 1. November 2010, 12:54:53 schrieb Andrew:
> Hi all.
> I have done supp
01.11.2010 22:07, KP Kirchdoerfer пишет:
> Am Montag, 1. November 2010, 17:49:33 schrieb Andrew:
>> 01.11.2010 16:23, KP Kirchdoerfer пишет:
>>> Am Montag, 1. November 2010, 12:54:53 schrieb Andrew:
Hi all.
I have done support for multiple subarchs (or even different configs for
one
Am Montag, 1. November 2010, 17:49:33 schrieb Andrew:
> 01.11.2010 16:23, KP Kirchdoerfer пишет:
> > Am Montag, 1. November 2010, 12:54:53 schrieb Andrew:
> >> Hi all.
> >> I have done support for multiple subarchs (or even different configs for
> >> one subarch), and it seems that it will work OK.
01.11.2010 16:23, KP Kirchdoerfer пишет:
> Am Montag, 1. November 2010, 12:54:53 schrieb Andrew:
>> Hi all.
>> I have done support for multiple subarchs (or even different configs for
>> one subarch), and it seems that it will work OK.
>> Currently new subarch requires:
>> 1) record in KARCHS varia
Am Montag, 1. November 2010, 12:54:53 schrieb Andrew:
> Hi all.
> I have done support for multiple subarchs (or even different configs for
> one subarch), and it seems that it will work OK.
> Currently new subarch requires:
> 1) record in KARCHS variable in MasterInclude.mk with it's name
> 2) patc
Hi all.
I have done support for multiple subarchs (or even different configs for
one subarch), and it seems that it will work OK.
Currently new subarch requires:
1) record in KARCHS variable in MasterInclude.mk with it's name
2) patch file into linux package, with name
$(CONFIGNAME.config)-$(SUBA