Arnaud Charlet wrote:
The idea currently is to make these values
explicit so that when people read system.ads, they know right away what
the right value is.
That's "when people read system.ads", not "when people read
system-linux-x86.ads". In other words, he's not necessarily against
automatically generating system.ads from other means, for example using
configure tests. Which, I repeat, comes out naturally if the RTS build is
confined in libada.
Right, that's one possibility, although people seem to be focusing
in system.ads alot, which is actually only the tip of the iceberg, and not
a real issue per se.
Do you really need to run programs? Most of gen-soccon can be done by
running Ada source code through the C pre-processor and massaging the
output. In fact, the code that would be passed through cpp strongly
resembles gen-soccon.c itself.
Agreed. But the current procedure generates a program which
generates the output.
We have actually made such a change recently, still need to contribute it.
For RTEMS, we build everything including the OS itself from
source in sequential order. The .h files for the network stack
are not available when the tools are built so the file can't be
generated automatically during the Ada build.
I don't think that's a big deal as long as you are aware that
at least one target can't generate the file on the fly.
Arno
--joel
