On Wed, Aug 15, 2007 at 02:30:31PM +0200, Stefan Reinauer wrote:
- migrate use of #include to separate compilation and standard linking?
not possible, unfortunately, because we're not using gcc for the raminit part but romcc. It has to be one big mess to work :-(
I don't understand. You mean the same code is used by different compilers, or that romcc can't handle multi-object linking?
Btw I thought that romcc was being deprecated in favour of cache-as-ram.
- modify util/newconfig/config.g to automatical scan C files and add the dependencies for #includes?
That would be neat.
I wonder whether it might make more sense to put effort in v3 though, as v2 might just go away quicker that way.
Unfortunately I'm python illiterate. Does v3 use the same code?
<GPLv2> I know my rights; I want my phone call! <DRM> What use is a phone call, if you are unable to speak? (as seen on /.)
That's a good one!
:-)