comp.lang.ada
 help / color / mirror / Atom feed
From: support@PublicPropertySoftware.com
Subject: Re: GWindows 1.1 Released
Date: Tue, 11 Mar 2003 08:48:32 -0800
Date: 2003-03-11T08:48:32-08:00	[thread overview]
Message-ID: <3E6E1360.8EED314@PublicPropertySoftware.com> (raw)
In-Reply-To: 17cd177c.0303110137.278ad535@posting.google.com

Gautier wrote:
> 
> Al:
> 
> > If I don't set Ada_Include_Path, how does the compiler find the
> > gnatcom specs?
> 
> The compiler also uses the registry to find libraries. E.g. it
> is how it finds the Win32 bindings. You can see it with
> regedit or with the tool gnatreg (GUI variant in gwindows).

This is getting curious.

I searched the NT registry for 'gnatcom'; having gnatcom installed in
L:\Ada\GnatCom. I figured that this search would find the path if
it is stored in there. I found an entry in:

	HKLM\Software\Microsoft\Windows\CurrentVersion
	   \AppPaths\GnatCom1.3p\		

With a value for path that pointed into L:\Recycler\, ie the trash
for the drive that gnatcom was installed on.  Probably not good.
I didn't set it to point at the trash.  What's up?  IDK.

I deleted the entry and re-ran the gnatcom install.  The installer
did not re-create the entry.

So, I go to add\remove programs to try to uninstall gnatcom, and it
has some old pointer to a previous version of gnatcom on another
drive, and it won't uninstall.  (The registry is evil, particularly
if you don't uninstall before re-installing.)  

So, I go searching again for gnatcom in the registry, trying to find
this old pointer to another drive to get rid of it, and I find that
the gnatcom re-install has added a new setting:

	HKLM\SOftware\Ada Core Technologies\GNAT\Standard Libraries
		GNATCOM = L:\Ada\Gnatcom\Bindings

This wasn't there until I just reinstalled (I'm almost sure).
Will GWindows make install with this new setting and no 
Ada_Include_Path?  No, but it does give us something else 
interesting to consider:

gnatbind -aO./ -aO../../bindings/ -I- -x gnatreg.ali
gnatlink gnatreg.ali
ld: cannot find -lcomctl32
gnatlink: cannot call I:\GNAT\BIN\gcc.exe
gnatmake: *** link failed.
make[2]: *** [gnatreg] Error 4
make[2]: Leaving directory `L:/Ada/gwindows/tools/gnatreg'
make[1]: *** [gnatreg] Error 2
make[1]: Leaving directory `L:/Ada/gwindows/tools'
make: *** [tools] Error 2


This machine must be haunted.  This makefile ran yesterday
afternoon just fine without hitting this error. LibComCtl32.a 
is surely in my I:\Gnat\Lib\Win32 directory.  

I uninstall and reinstall GnatWin-3.15p.exe to see if that fixes
anything, then re-run Gwindows 'make ANSI=1 install'.  It works
fine with no ADA_INCLUDE_PATH now that the GnatCom registry
setting (above) is there.  Why it wasn't there yesterday is
just another one of those mysteries.


Al



  reply	other threads:[~2003-03-11 16:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-10 22:09 GWindows 1.1 Released David Botton
2003-03-11  0:50 ` support
2003-03-11  7:46   ` Martin Dowie
2003-03-11  9:37   ` Gautier
2003-03-11 16:48     ` support [this message]
2003-03-11 16:22   ` David Botton
2003-03-11 16:51     ` support
  -- strict thread matches above, loose matches on Subject: below --
2003-03-11 18:59 David Botton
2003-03-11 18:54 David Botton
2003-03-10  4:24 David Botton
2003-03-10 12:07 ` Martin Dowie
2003-03-10 14:25   ` David C. Hoos
2003-03-10 16:32   ` David Botton
2003-03-10 16:49 ` chris.danx
2003-03-10 18:39   ` support
2003-03-11  2:39     ` R. Srinivasan
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox