Re: GNAT on a multiboot computer

["Warren W. Gay VE3WWG" <ve3wwg@NoSPAM.cogeco.ca>]

Anders Wirzenius wrote:

> "Warren W. Gay VE3WWG" <ve3wwg@NoSPAM.cogeco.ca> writes:
>>Adrien Plisson wrote:
>>>Anders Wirzenius wrote:
...
>>>>To me it seems that this configuration has to be pretty much the same as
>>>>what you get when you install GNAT on another partition than on the
>>>>traditional C:. I have never done such an installation of GNAT.
>>>
>>>i think i never installed GNAT on the traditional location. there is
>>>no problem until you want to compile and install some add-ons like
>>>glade, polyorb or such, since cygwin tools do not like long
>>>filenames and weird locations. in this case 'you have to find the
>>>way'...
>>
>>I have developed a fondness for C:\opt for non-cygwin software:
>>
>>   c:\opt\gnat
> 
> So what environmental values did your installation create?
> PATH=?
> ADA_INCLUDE_PATH=?
> What's in the registry under [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core
> Technologies]?

GNAT is non-cygwin, so it takes Windows pathnames as I
specified it at install time. But here
are my registry entries that you were interested in:

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT]
"ROOT"="C:\\opt\\gnat"
"FOLDER"="GNAT Public Version"
"GUID"="{CB2174B0-F84A-11D4-ACAA-0010A4E31500}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT\3.15p]

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT\Standard Libraries]
"WIN32ADA"="C:\\opt\\gnat\\Bindings\\Win32Ada"
"WIN32"="C:\\opt\\gnat\\lib\\win32"


Obviously there is some care required when choosing compilers
when working in the cygwin bash shell. You either don't use
GNAT, or you use it by putting the bin directory first on the
PATH (or at least before cygwin's gcc).

To make things more complicated now, you can install ada-aware
versions of gcc under cygwin, as I have done. So you do have
to keep your wits about you!

> ...?
> If I make manually similar configuration entries as you got when
> installing in c:\opt then I should be safe. (?)
> I succeeded to get GNAT working with help from Adrien :), but I am
> curious about how my entries is compared to for instance the result of
> an installation to c:\opt, which is not the default (C:\GNAT).

ACT's own install program lets you choose - so just choose away! Just
avoid blanks in the directory names. 8-)

In a multiboot situation, if the drive letter changes, this will
create problems I think (I guess that was your point). Without
having thought about this much, one possible solution is to
use *.reg files as outlined below (using regedit):

Save your registry settings like I did above. When you boot
the OS that needs it as D: instead of C:, run an edited version
of your gnat.reg file that you saved. When you start the other
OS, run its version of gnat.reg that specifies C: instead. That
will at least let you switch between the two.

To fix the path, you'll have to locate another registry entry,
and do the same thing.

> I don't want to change the installation on the XP hardisk (see previous
> postings). I just want to make necessary configurations on the win 2003
> hardisk to be able to use the existing GNAT installation when the
> computer is booted as a win 2003 installation.

Well, the *.reg files I mentioned above might work good enough
for you. Save the registry entries in question and substitute
drives as appropriate. I think you might be able to put the *.reg
files in your startup folder, but if not, you can double-click them
to make them "effective" (I am sure there are other ways this can
be automated).


> The 2003 installation is only used for a .NET course and is likely to be
> deleted when the training is over (I prefer AWS over .NET :)). 
> 
> Anders

Keep the original .reg files so that you can "revert" back to the
original settings.

Hope that helps, Warren.
-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg