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.2 required=5.0 tests=BAYES_00,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,d427e558e79b637a X-Google-Attributes: gid103376,public From: "David C. Hoos, Sr." Subject: Re: GNAT NT 3.09 Search Path Date: 1997/02/17 Message-ID: <01bc1ccb$efa2e460$278c71a5@dhoossr.iquest.com> X-Deja-AN: 219363364 Distribution: world References: <33083429.1726@netspace.net.au> Content-Type: text/plain; charset=ISO-8859-1 Organization: Ada95 Press, Inc. Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1997-02-17T00:00:00+00:00 List-Id: Hi Barry and Jackie, I don't know whether this is documented, or not, but it's inferred by the background (stated several times in this group and on gnat-list prior to the release of gnat3.09 for win32). Gnat3.09 (and future gnats) for win32 (Windows 95 and Windows NT) is built on gnu-win32, rather than native Win32, in order to simplify the ports. Gnu-win32 is a project of Cygnus (www.gygnus.com) the folks who provide commercial support for GNU (Free Software Foundation) software. Gnu-win 32 is free, and provides a UNIX-like interface (both programming and user interfaces). It is currently in Beta 17 release, and still has some rough spots, as well as some unimplemented features and utilities. Not only does gnu-win32 simplify the porting of gnat, it also simplifies the porting of other UNIX software to Win32. The gnat3.09 release includes that portion of gnu-win32 necessary to support gnat (provided everything is on drive C). To support use of drives other than drive C, you need at least the mount executable from the gnu-win32 project. This can be obtained from ftp.cygnus.com/pub/gnu-win32/gnu-win32/cygwin-extras.tar.gz. The .gz suffix signifies a "gzipped" file which needs to be unzipped with "gunzip" or an equivalent. If you prefer to use a web browser, the URL becomes "ftp://ftp.cygnus.com/pub/gnu-win32/gnu-win32/ for the directory where all of the latest release of gnu-win32 resides. The best utility for unzipping is winzip32 (shareware -- available for free evaluation -- available by anonymous ftp from "ftp.winzip.com/winzip95.exe" or by Web browser from "http://www.winzip.com/wz62.cgi"), but you can get gunzip.exe free from the same directory as the gnu-win32 stuff at cygnus.com. The .tar file which results from running gunzip, can be "untarred" by tar.exe, available from the same gnu-win-32 directory. The WinZip program does unzipping, untarring, and a whole host of other things. The bottom line of all this is that the environment variable values recognized by gnat3.09 need to be in UNIX-style format. First, though, your drive (or at least the directory) with you source needs to be mounted. The syntax is "mount ". For example, you could say "mount G:\ /G". Then ADA_INCLUDE_PATH=/G/x:/G/y:G/z will work. Note that UNIX-style paths are COLON-SEPARATED pathnames, not semicolon-separated as in DOS. Your mount commands are remembered next time you restart your computer. The environment variables may be either System or User, according to the scope in which you wish them to be visible. By the way, I have tried all of this on both Windows 95, and Windows NT 4.0 (released, and with SP 2). All OK. Please excuse the verbosity, but I wanted to provide the background for what appears to work differently from what is stated in the documentation I've seen. I plan to put this information, as well as a number of other things I discovered the hard way (e.g., using the win32ada bindings with gnat3.09) up on my website (www.ada95.com) in a day or two. -- David C. Hoos, Sr., http://www.dbhwww.com http://www.ada95.com Barry and Jackie Schiff wrote in article <33083429.1726@netspace.net.au>... > Anybody having problems with ADA_INCLUDE_PATH and ADA_OBJECTS_PATH > under NT 3.09. I have installed GNAT 3.09NT on drive C > (as required per > instructions) which on my system happens to be a FAT partition. > My development occurs on drive G (an NTFS) partition. > Now say I am compiling my_file in directory x which references > files in directory y and z all on drive G. > > If I do: > > gnatmake -c -Ig:\y -Ig:\z my_file > > all goes well. But If I > don't give these switches it does not work. > I have tried setting the following environment variables as follows: > > ADA_INCLUDE_PATH=g:\z;g:\y;g:\z > ADA_OBJECTS_PATH=g:\z;g:\y;g:\z > > I have tried setting these as User environment variable. I have also > tried > them as System Environment Variables. Neither worked. > > Note: x y and z are long directory names. > I am running NT 4.0 Workstation - Released Version. > > It appars as if the compiler does not see the > environment variables. I'm sure it's something dumb > on my part. Any help greatly appreciated. > > --Barry >