From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: ***
X-Spam-Status: No, score=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID,
	RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no
	version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,63ff9743b4a53a7c,start
X-Google-Attributes: gid103376,public
From: "kgamble" <kgamble@ricochet.net>
Subject: Filenames vs Compilation Names
Date: 1997/06/25
Message-ID: <01bc8189$c96567a0$7175b89e@Ken'slaptop.ssd.loral.com>#1/1
X-Deja-AN: 252506320
Organization: Space Software Systems
Newsgroups: comp.lang.ada
Date: 1997-06-25T00:00:00+00:00
List-Id: <comp.lang.ada>


It appears that gnat.adc (useful when filenames and unit names do not
match) only works when all sourcefiles are stored in a common directory.

I am porting a large Ada program to OS2 using GNAT 3.09. Files are
organized into many subdirectories and usually have filenames that do not
match compilation names. In the GNAT documentation, the work around is to
use Source_File_Name pragmas stored in a file named gnat.adc

Even though this appears to work when compiling files that are in the same
subdirectory as the gnat.adc file, it doesn't appear to work for files
outside the subdirectory. That is, a compilation unit having a "with
clause" for a unit stored in another subdirectory, the compiler will not
check the gnat.adc for remapping of the filenames. I would have thought
that the compiler would be capable of searching gnat.adc files stored in
other directories. 

Has anyone had any success with using gnat.adc for files stored in
different directories?