[oe] [PATCH 4/4] Renamed prefix_native, bindir_native, etc using hyphens

Douglas Royds douglas.royds at tait.co.nz
Thu Mar 18 20:48:59 UTC 2010


Frans Meulenbroeks wrote:
> 2010/3/18 Douglas Royds <douglas.royds at tait.co.nz>:
>   
>>   - Avoids clashing with the machine override when MACHINE=native
>>   - bindir_cross similarly renamed for consistency
>>
>>     
> [...]
>   
>>  # Path prefixes
>>  base_prefix = "${STAGING_DIR_NATIVE}"
>> -prefix = "${STAGING_DIR_NATIVE}${prefix_native}"
>> -exec_prefix = "${STAGING_DIR_NATIVE}${prefix_native}"
>> +prefix = "${STAGING_DIR_NATIVE}${prefix-native}"
>> +exec_prefix = "${STAGING_DIR_NATIVE}${prefix-native}"
>>     
>
> [...]
>
> Shouldn't we then for consistent naming also go to exex-prefix etc ?

In the spirit of keeping a single patch for a single purpose, I have not 
modified anything that is not required to fix the problem at hand (um, 
except for bindir_cross). I have only modified the variable names that 
were modified in Richard's commit "Start removal of layout_* variables 
and replace these with new mechanisms to allow nextgen SDK generation 
(from Poky)":

    http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=bea72c2fecde175add169bb55df1922b048030c8

Any renaming of base_prefix, exec_prefix, base_bindir, target_datadir, 
&c is a separate matter. Note that some of these names are imposed on us 
by Autotools convention. This is why these variables are in lower case 
in the first place:

    http://www.gnu.org/prep/standards/html_node/Directory-Variables.html#Directory-Variables

Douglas.

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================





More information about the Openembedded-devel mailing list