Re: Configurable Run Time without GPR Tools

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 2019-11-05 06:47, Daniel Way wrote:
> I'm trying to write a motor control application running on an ARM Cortex-M0+. I've installed GNAT CE 2019 targeting arm-eabi and I can compile various test programs using the -I switch to specify a system.ads file.
> 
> To create an executable, I believe I will need an installed run time, but I find the way these are handled in GNAT to be confusing. I'd like to package all library sources in a project subfolder to make sharing everything easier, however, the deeply nested library structure that comes with GNAT is overwhelming.

Why? You need not to care about these libraries.

> - I'd like to know how others prefer to package the library with application code

Your third-party libraries you can place anywhere. It is not a good idea 
to mix them with the libraries that come with the cross-compiler tool 
chain. In out project we keep and maintain them separate, because the 
former come updated with the compiler wavefronts and the latter with our 
tinkering on the target. These are two completely independent cycles.

> - are the GPR tools absolutely necessary for building a run time, or is there another way to compile standard library packages?

They are not necessary. You can use gnatmake or even just gcc and 
gnatbind etc. Yet gprbuild saves a huge amount of time and work, 
especially for large projects. It is also quite powerful and safe when 
it comes to multiple targets within same project. It really pays off to 
learn it a bit.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de