[M3devel] Arch-independent derived files (Re: multiarch)

[Mika Nystrom]

Going in the "other direction" it might be nice to have different
derived directories for different compilers, e.g., CM3 and PM3, or
different versions of CM3.

Not something that is really necessary for anyone, I'm sure, but
it seems like a flexible mechanism for "derived" directories might
be able to handle that too...

     Mika

"Rodney M. Bates" writes:
>This may only be peripherally related, but since this discussion
>has come up:
>
>I have long wished for a directory, neither src, nor the architecture
>directory, for files that are mechanically generated but not
>target dependent.  I have an application where there are several
>machine-generated files containing Modula-3 "source" code.
>
>It's "source code", in the sense that it is input to the compiler, but  not
>"source code", in the sense that it is not written by a human using
>an editor.  Some existing quake commands for instantiating generics
>do similarly.  Neither place is entirely appropriate for these files.
>
>I have gone through a series of kludgy ways of handling this.  Right
>now, I have them in a directory "derived", beside "src", with lines in
>m3makefiles that look, e.g., like:
> 'implementation("../derived/M3InitTokStrings")'.
>
>But the instantiating quake functions put generated source code in
>the arch directory, and sometimes unnecessarily regenerate it.
>
>Just something that it would be nice to clean up.
>
>hendrik at topoi.pooq.com wrote:
>> It seems relevant to out multiarchitecture system that Debian and Ubuntu 
>> are currently also struggling to put together a multiarchitecture 
>> system.
>>
>> Current thinking seems to be posted at
>> https://wiki.ubuntu.com/MultiarchSpec
>>
>> The stimulus for this work seems to be having 32-bit and 64-bit programs 
>> coexist on the same AMD-64 system.  But it also deals with questions 
>> like MIPS systems having at least three different ABIs.
>>
>> Have a look.
>>
>> -- hendrik
>>
>>
>>