GNAT NT 3.09 Search Path

GNAT NT 3.09 Search Path

[Barry and Jackie Schiff]

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

Re: GNAT NT 3.09 Search Path

[Robert Dewar]

Barry asks about

<<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.>>

When using GNAT 3.09 on NT, you need to use the Unix format for
the path names. We will update the readme to include this and
some other pointers on using the NT version of GNAT. In general,
remember that GNAT on NT is quite intentionally Unix like, this
is not the only place where Unixism's are apparent!

Re: GNAT NT 3.09 Search Path

[David C. Hoos, Sr.]

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 <dos-pathname> <UNIX-pathname>".  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 <schiff@netspace.net.au> 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
> 

Re: GNAT NT 3.09 Search Path

[Richard Kenner]

In article <01bc1ccb$efa2e460$278c71a5@dhoossr.iquest.com> "David C. Hoos, Sr." <david.c.hoos.sr@ada95.com> writes:
>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.

I don't think this is correct.  The syntax "//g/directory/file"
is supported (this is for compatibility with the NT Posix subsystem).
I can't test this since I only have one drive, though.

Re: GNAT NT 3.09 Search Path

[David C. Hoos, Sr.]

I stand corrected.  The UNIX-like utilities which come with the Microsoft
Resource Kit for Windows NT (1995 version) do not support the //D/ syntax. 
Those that are part of the gnu-win32 toolset do.

I do find it convenient, however to use the mount command.  E.g., I have
mounted V:\win32ada as /win32ada, so that path names embedded in scripts,
or in environment variable values can be drive-independent.

Thanks for pointing out my error.
David C. Hoos, Sr.
http://www.ada95.com
http://www.dbhwww.com

Richard Kenner <kenner@lab.ultra.nyu.edu> wrote in article
<5e9om6$hmg$1@news.nyu.edu>...
> In article <01bc1ccb$efa2e460$278c71a5@dhoossr.iquest.com> "David C.
Hoos, Sr." <david.c.hoos.sr@ada95.com> writes:
> >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.
> 
> I don't think this is correct.  The syntax "//g/directory/file"
> is supported (this is for compatibility with the NT Posix subsystem).
> I can't test this since I only have one drive, though.
> 

Re: GNAT NT 3.09 Search Path

[William Paul Berriss]

Hi

I have a found similar problem with GNAT 3.09 for Win 95 on a PC.

If I put a line like 
set ADA_INCLUDE_PATH=C:\windows;C:\ada\eeg;
plus other directories in a .bat file and run that before running
gcc, gcc cannot find the necessary library files in the eeg directory.

BUT

If I type the command set ADA_INCLUDE_PATH=C:\ada\eeg at
the DOS prompt myself, just before running gcc then all is OK, 
it finds files OK.

Is this because I have just one directory in the ADA_INCLUDE_PATH
and so I have no problems with forward slashes and colons?
I will try this ASAP.

I hope so as it really confused me.


Will Berriss
=============

-- 

W P Berriss                 E-mail: W.P.Berriss@reading.ac.uk
Department of Engineering
The University of Reading
Whiteknights
Reading                     Tel:  0118 987 5123 
Berkshire                     (+44 118 987 5123 outside UK)
RG6 6AY    
England                     Fax:  0118 931 3327    

World Wide Web Home Page: 

http://www.elec.rdg.ac.uk/people/postgrads/will.html

Re: GNAT W95 3.09 Search Path

[William Paul Berriss]

Hi

I should have said that I installed GNAT in C:\Usr as
instructed, and I put C:\usr\bin in my PATH varialbe.
So, the problem exists with the C drive too.

-- 

W P Berriss                 E-mail: W.P.Berriss@reading.ac.uk
Department of Engineering
The University of Reading
Whiteknights
Reading                     Tel:  0118 987 5123 
Berkshire                     (+44 118 987 5123 outside UK)
RG6 6AY    
England                     Fax:  0118 931 3327    

World Wide Web Home Page: 

http://www.elec.rdg.ac.uk/people/postgrads/will.html

Re: GNAT NT 3.09 Search Path

[Stephen Leake]

William Paul Berriss wrote:
> 
> If I put a line like
> set ADA_INCLUDE_PATH=C:\windows;C:\ada\eeg;
> plus other directories in a .bat file and run that before running
> gcc, gcc cannot find the necessary library files in the eeg directory.
> 
> BUT
> 
> If I type the command set ADA_INCLUDE_PATH=C:\ada\eeg at
> the DOS prompt myself, just before running gcc then all is OK,
> it finds files OK.

It sounds like you are running under bash, which spawns a sub-process
for each command. So in the first scenario, you define ADA_INCLUDE_PATH
in a sub-process, which then exits, losing the definition. In the second
scenario, you define ADA_INCLUDE_PATH in your main process, and all is
well.

If you are running in a DOS window, I'm confused too. Perhaps you could
post an exact log of what you type; that should make things clearer.
 
> Is this because I have just one directory in the ADA_INCLUDE_PATH
> and so I have no problems with forward slashes and colons?
> I will try this ASAP.
> 
> I hope so as it really confused me.

This is one reason I always use a makefile, and explicitly put
"-I/ada/eeg" etc in the commands. That way, when I give the make file to
someone else, I never have to remember to also give them the
ADA_INCLUDE_PATH definition.
> 
> Will Berriss
> =============

-- 
- Stephe

Re: GNAT NT 3.09 Search Path

[Barry and Jackie Schiff]

Thanks to people in this group the answer is as follows:

	make ada_include_path and ada_objects_path =

		//g/dir://g/other_dir


------------ Things that did not work for me ---------

		not:

		g:\dir;g:/other_dir 

		and not:

		g:/dir;g:/other_dir

---------------------------

I am told that another solution is to use the mount
gnu utility which would allow such declaration to be
drive independent. Again the unix style slash is used
and colons not semi-colons.


--Barry Schiff

Re: A Solution to GNAT W95 3.09 Search Path

[William Paul Berriss]

Hi

I have found a solution to MY path problem 
on GNAT 3.09 for Windows 95.


1. The  PATH variable should be set as normal, using backslashes \
and using semi-colons ;  to separate the directories listed
in the path.



2.  BUT for the ADA_INCLUDE_PATH and the ADA_OBJECTS_PATH 
   I have used forward slashes / and colons :

I tried it with just forward slashes and semi-colons to
separate the directories but this did NOT work.

The solution is to use  COLONS :   to separate the directories
that you list in your ADA_* paths.
COLONS  : are the important part, you *may*
not need to use forward slashes (but I did and mine works.)

I hope this helps somebody, as people are often helping me
on this newsgroup.


Will Berriss
============
-- 

W P Berriss                 E-mail: W.P.Berriss@reading.ac.uk
Department of Engineering
The University of Reading
Whiteknights
Reading                     Tel:  0118 987 5123 
Berkshire                     (+44 118 987 5123 outside UK)
RG6 6AY    
England                     Fax:  0118 931 3327    

World Wide Web Home Page: 

http://www.elec.rdg.ac.uk/people/postgrads/will.html

Re: GNAT NT 3.09 Search Path

[John English]

William Paul Berriss (W.P.Berriss@reading.ac.uk) wrote:
: If I put a line like 
: set ADA_INCLUDE_PATH=C:\windows;C:\ada\eeg;
: plus other directories in a .bat file and run that before running
: gcc, gcc cannot find the necessary library files in the eeg directory.

: BUT

: If I type the command set ADA_INCLUDE_PATH=C:\ada\eeg at
: the DOS prompt myself, just before running gcc then all is OK, 
: it finds files OK.

Are you running the batch file in the same process as you run gcc
from? Otherwise, the environment variables will be set up in the
process that runs the .bat file, and gcc will run in a process
which *doesn't* have them set up. Try (a) a batch file which sets
everything up and then runs gcc, or (b) call the batch file from
your autoexec.bat (so that it's in the parent environment for all
other processes).

HTH.

---------------------------------------------------------------
 John English              | mailto:je@brighton.ac.uk
 Senior Lecturer           | http://www.comp.it.bton.ac.uk/je
 Dept. of Computing        | fax: (+44) 1273 642405
 University of Brighton    |
---------------------------------------------------------------