Re: GWindows 1.1 Released

["David Botton" <David@Botton.com>]

Very strange indeed....

I would recommend using: gnatcom-20020610.zip from the AdaPower site
http://www.adapower.com/gnatcom

David Botton

----- Original Message -----
From: <support@PublicPropertySoftware.com>
Newsgroups: comp.lang.ada
To: <comp.lang.ada@ada.eu.org>
Sent: Tuesday, March 11, 2003 11:48 AM
Subject: Re: GWindows 1.1 Released


> 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
> _______________________________________________
> comp.lang.ada mailing list
> comp.lang.ada@ada.eu.org
> http://ada.eu.org/mailman/listinfo/comp.lang.ada