Home/ Questions/Q 944279
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T22:34:02+00:00

I’m still new to the Ada programming world so forgive me if this question

  • 0

I’m still new to the Ada programming world so forgive me if this question is obvious.

I am looking at developing an application (in Ada, using the features in the 2005 revision) that reads from the serial port and basically performs manipulation of the strings and numbers it receives from an external device.

Now my intention was to likely use Florist and the POSIX terminal interfaces to do all the serial work on Linux first….I’ll get to Windows/MacOS/etc… some other time but I want to leave that option open.

I would like to follow Ada best practices in whatever I do with this. So instead of a hack like conditional compilation under C (which I know Ada does not have anyway) I would like to find out how you are suppose to specify a change in package files from the command line (gnatmake for example)?

The only thing I can think of right now is I could name all platform packages exactly the same (i.e. package name Serial.Connector with the same filenames) and place them in different folders in the project archive and then upon compilation specify the directories/Libraries to look in for the files with -I argument and change directory names for different platforms.

This is way I was shown for GCC using C/C++…is this still the best way with Ada using GNAT?.

Thanks,
-Josh

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That’s a perfectly acceptable way of handling this kind of situation. If at all possible you should have a common package specification (or specifications if more than one is appropriate), with all the platform-specific stuff strictly confined to the corresponding package body variations.

    (If you did want to go down the preprocessor path, there’s a GNAT preprocessor called gnatprep that can be used, but I don’t like conditional compilation either, so I’d recommend staying with the separate subdirectories approach.)

    • 0