[Info-vax] cross tools and CLD scope

[Craig A. Berry]

On 10/18/21 12:38 PM, Simon Clubley wrote:
> On 2021-10-18, Robert A. Brooks <FIRST.LAST at vmssoftware.com> wrote:
>> On 10/18/2021 12:51 PM, David Jones wrote:
>>> On Monday, October 18, 2021 at 12:10:04 PM UTC-4, Craig A. Berry wrote:
>>>> That's all impressive and scary. Luckily editing .FIRST or the code
>>>> that generates it to include the cross tools set-up got me as far as I
>>>> can get with that mechanism. Then I was on to cases where code is
>>>> generated that needs to be compiled and run natively to probe for
>>>> features that will then be used to generate additional code that will
>>>> need to be built with the cross tools. It's not going to be pretty.
>>>
>>> My solution certainly isn't pretty:
>>
>> [...] stuff removed
>>    
>> That seems more complicated than it needs to be
>>
>> You can remove the cross-build changes this way . . .
>>
>> @sys$startup:X86_XTOOLS$SYLOGIN.COM "" "" "TRUE"
>>
>>
>> I also build a few layered products whose bootstrap tools need to run
>> on the build system, so I'm constantly flipping between native and
>> cross builds in the context of a build.
>>
> 
> Disclaimer: I am more familiar with the gcc approach to building
> and using embedded toolchains than I am with the LLVM approach
> to building them.
> 
> However, I am aware that clang uses target triples to select the
> target. Do the VSI cross-compiler toolchains also use target triples
> underneath the DCL commands ?
> 
> If so, is there any possibility of just invoking the tools directly,
> bypassing the DCL commands, and specify the target triple for x86-64
> VMS on the command line directly ?

The target triples seem very specific to clang and related front ends.
Given that the front ends for all the cross compilers are ports of the
existing VMS front ends and all of them have been made to believe there
is something resembling GEM under the hood even though it's a
GEM-to-LLVM compatibility layer, what you're suggesting sounds highly
improbable.