About the target/host situation

Jonathan Gibbons jonathan.gibbons at oracle.com
Mon Jun 11 09:42:58 PDT 2012


On 06/11/2012 09:30 AM, Magnus Ihse Bursie wrote:
> On 2012-06-04 11:47, Magnus Ihse Bursie wrote:
>> Fredrik and others, please note that this does not mean that this is 
>> the final say in the discussion! It just means that we need to 
>> resolve the current block on our work in build-infra. The fact that 
>> either this or Fredriks solution is the current one in build-infra 
>> right now should carry no weight when coming to a final decision on 
>> how the matters should be! As far as this is a part of the 
>> discussion, it is to bring an example on how the --jdk-target option 
>> could be implemented.
>
> Fredrik, Erik and I have now agreed to use the term "OpenJDK target" 
> throughout the build system (in variables, configure options and 
> documentation) to refer to the platform which the generated product 
> will run on (the target platform). As a consequence, the internal 
> variables previously named HOST_ (e.g. HOST_OS), and temporarily named 
> TARGET_ (e.g. TARGET_OS), are now named OPENJDK_TARGET_ (e.g. 
> OPENJDK_TARGET_OS). While more cumbersome to write, there is no risk 
> of mixing this up with the autoconf sense of of "target". We believe 
> this to be a fruitful compromise, and hope the rest of you agrees. :-)
>
> I will shortly push changes to the build-infra forest inplementing this.
>
> /Magnus

Sounds like a good, clear, and unconfusing solution!  Well done, guys.

-- Jon



More information about the build-infra-dev mailing list