[LinuxBIOS] make dependencies and C includes

[Robert Millan]

Hi!

I've observed that C #include'd files such as raminit.c aren't represented
in make dependencies, resulting in them not being recompiled after a
modification.

I'm not sure what would be the proper solution:

- add the dependency manually in the corresponding Config.lb files?
  - migrate use of #include to separate compilation and standard linking?
  - modify util/newconfig/config.g to automatical scan C files and add
    the dependencies for #includes?

[Stefan Reinauer]

* Robert Millan  [070815 14:18]:
> add the dependency manually in the corresponding Config.lb files?

possible but nasty
> 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 :-(
> 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.
> <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!

Stefan

[Robert Millan]

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!

:-)

[ron minnich]

On 8/15/07, Robert Millan  wrote:
> I don't understand.  You mean the same code is used by different compilers, or
> that romcc can't handle multi-object linking?

There is no mem, hence no stack, hence romcc is 100% inline.
multi-object linking has no meaning in romcc.
> Btw I thought that romcc was being deprecated in favour of cache-as-ram.

yes.
> Unfortunately I'm python illiterate.  Does v3 use the same code?

V3 is Kconfig. NO NO NO NO NO Python in V3! Oh happy day!

ron

[ron minnich]

On 8/15/07, Robert Millan  wrote:
> Hi!
>
> I've observed that C #include'd files such as raminit.c aren't represented
> in make dependencies, resulting in them not being recompiled after a
> modification.

V3. We're trying as hard as we can to get the first ports out, at
which point all life is better ...

thanks

ron