Re: Resolving Long Filenames for Packages

[alexander@xn--junivrs-e1a.com]

Actually, in using the `gprbuild` command, should I happen to use filenames that does not mirror the package name, the compiler tells me that the "file for the specific package" wasn't found:

`main.adb:1:06: file "expressions-parser-automata-automaton_x.ads" not found`

This occurs, for instance, when the package Expressions.Parser.Automata.Automaton_X is located in a file named automaton_x.ads (as well as a file for the body: automaton_x.adb).

This is a default behavior as according to "http://docs.adacore.com/live/wave/gnat_ugn/html/gnat_ugn/gnat_ugn/the_gnat_compilation_model.html#file-naming-rules". On that page, they also discuss how one might use non-default file-names: "http://docs.adacore.com/live/wave/gnat_ugn/html/gnat_ugn/gnat_ugn/the_gnat_compilation_model.html#using-other-file-names", but using two pragmas per non-default filename seems a slight bit excessive for something that should be a simple task.

Should anyone have any idea as to how this should be handled with GNAT's `gprbuild` with a little more ease, that information would be highly appreciated!

Thank you, so far, Robert Eachus for recommendations on how the file naming might be done.

G. B. I do briefly remember not being required to use standard filenames during compilation with the `gnatmake` command for GNAT, but in switching to `gprbuild` and the `.gpr` project files to simplify the handling of projects, I'm still to find a means of naming files whatsoever I may want.