Re: GNAT user-specified (via Raise_Exception) warning message size limit

[Simon Wright <simon@pushface.org>]

briot.emmanuel@gmail.com writes:

> As I am sure Simon already knows, but might be useful for others (it
> doesn't solve the problem highlighted by Simon, though):
>
> You can actually use gprbuild to recompile locally the bodies of
> runtime files.  You just have to put them in your source directories,
> and change the project file to make sure the file is compiled with
> -gnatg.  I have done that quite often for System.Memory
>
>    project Default is
>         package Compiler is
>              for Switches ("s-memory.adb") use ("-gnatg");
>         end Compiler;
>    end Default;

I don't think I've ever done this - failing to do it would explain why,
even after precompiling s-stratt.adb with -gnatpg (which gnatmake -a
did), gprbuild with the default .gpr wouldn't build.

> This trick however doesn't work for specs, since it doesn't recompile
> all runtime units that depend on them unless they are part of the
> project.  You might get away with creating a "runtime.gpr" project
> that uses for source dirs the runtime location, and forces the -gnatg
> switch.

I suppose other runtime units would need recompiling if any part of this
body was inlined.