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

[jay.krell at cornell.edu]

I have seen systems head that way, only to abandon it, for the sake of  
consistency and simplicity -- outputs all in one more known place, and  
for concurrency -- build multiple architectures without them stomping  
on each other. Are the files large or slow to be generated?

  I am on the fence. I like identifying what is the same and removing  
duplication. But if it is automated and fast, less motivation.

Considering more of the system, we do parse identical .i3 files per- 
platform.  The middle end work is also almost the same for every  
platform. But judging from the overall NT386 speed, this is all very  
fast.

  - Jay (phone)

On Jul 7, 2009, at 1:02 PM, "Rodney M. Bates" <rodney.m.bates at cox.net>  
wrote:

> 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
>>
>>
>>
>
>