GNAT on a multiboot computer

GNAT on a multiboot computer

[Anders Wirzenius]

Hi,

Does anyone have a good advice on how to set up the
GNAT compiler system on a multiboot Windows computer?

<context>
I have a multiboot computer (Win XP, Linux Debian, Win 2003).
Each of these OSes reside on its own physical harddisk. The boot
is guided by a lilo which assigns the appropriate harddisk
as the boot disk for each OS.
GNAT was installed when the computer was booted as XP. The 
installation was done using the gnat-3.15p-nt.exe installation
program and works fine. The files were copied to C:\GNAT\...
</context>

Now I want to use GNAT when the computer is booted as Win 2003.
The boot disk is E: with environment variable SystemDrive=E:.

I have set following variables in Win 2003:
ADA_INCLUDE_PATH=C:\GNAT\lib\gcc-lib\pentium-mingw32msv\2.8.1\adainclude
ADA_OBJECTS_PATH=C:\GNAT\lib\gcc-lib\pentium-mingw32msv\2.8.1\adalib
Path=C:\GNAT\bin;C:\GNAT\lib\gcc-lib\pentium-mingw32msv\2.8.1;
E:\WINDOWS\system32;E:\WINDOWS;E:\WINDOWS\system32\WBEM;
E:\oracle\product\10.1.0\Db_1\bin;
E:\oracle\product\10.1.0\Db_1\jre\1.4.2\bin\client;
E:\oracle\product\10.1.0\Db_1\jre\1.4.2\bin;

, but I get still an error message (F: is a data partition on the
same physical hard disk as where E: resides):

F:\anders>gnatmake test
gnatbind -x test.ali
gnatlink test.ali
ld: cannot open crt2.o: No such file or directory
gnatlink: cannot call C:\GNAT\bin\gcc.exe
gnatmake: *** link failed.

crt2.o is found in
C:\GNAT\lib\gcc-lib\pentium-mingw32msv\2.8.1 and
gcc.exe is found in C:\GNAT\bin\,
both is in the PATH variable.

Any hints how to proceed?
Maybe Win 2003 access rights on the XP hard disk directories C:\GNAT\
play a role?

TIA
Anders

Re: GNAT on a multiboot computer

[Adrien Plisson]

Anders Wirzenius wrote:
> Any hints how to proceed?
> Maybe Win 2003 access rights on the XP hard disk directories C:\GNAT\
> play a role?

GNAT for windows sets up a bunch a registry keys which seems to act like a path.

You can find those keys under:
HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies

hope this helps...

-- 
rien

Re: GNAT on a multiboot computer

[Anders Wirzenius]

Adrien Plisson <aplisson-news@stochastique.net> writes:

> 
> GNAT for windows sets up a bunch a registry keys which seems to act
> like a path.
> 
> You can find those keys under: HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core
> Technologies
> 
> hope this helps...
> 
> -- rien

Tkanks, but I have not got any help from the registry.

These are from the "XP registry" (hardisk C:):

--------------------------------------------
[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies] "GCC"="C:\\GNAT"
"MINGW32"="@GCC" "GNAT"="@GCC" "VERSION"="3.15p" "BINUTILS"="@GCC"

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT]
"ROOT"="C:\\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]

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT]
"Root"="c:\\mgnat"

[HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT\Standard
Libraries] "DOTNET"="c:\\mgnat\\include"
------------------------------------------------

There is of course nothing in the "WIN 2003 registry" (E:) Maybe I could
copy the GNAT keys from XP to 2003?  Maybe the "ROOT"="C:\\GNAT" is
missing in 2003?

Anders

Re: GNAT on a multiboot computer

[Adrien Plisson]

Anders Wirzenius wrote:
> Tkanks, but I have not got any help from the registry.
> 
> These are from the "XP registry" (hardisk C:):
> 
> --------------------------------------------
> [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies] "GCC"="C:\\GNAT"
> "MINGW32"="@GCC" "GNAT"="@GCC" "VERSION"="3.15p" "BINUTILS"="@GCC"
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT]
> "ROOT"="C:\\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]
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT]
> "Root"="c:\\mgnat"
> 
> [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT\Standard
> Libraries] "DOTNET"="c:\\mgnat\\include"
> ------------------------------------------------
> 
> There is of course nothing in the "WIN 2003 registry" (E:) Maybe I could
> copy the GNAT keys from XP to 2003?  Maybe the "ROOT"="C:\\GNAT" is
> missing in 2003?

that what I was meaning... you can try to copy them from XP to 2003.
but BEWARE OF THE GUID key !! it seems to relate to uninstall informations, but 
on my machine I can also find a reference to this GUID in the ARPCache (!?! why 
is it referenced here !?!)

try and see !

-- 
rien

Re: GNAT on a multiboot computer

[Stephane Riviere]

On Tue, 26 Oct 2004 07:03:27 GMT, Anders Wirzenius
<anders@no.email.thanks.invalid> wrote:
>Does anyone have a good advice on how to set up the
>GNAT compiler system on a multiboot Windows computer?

You can use AIDE (Ada Instant Development Environment) for Windows
(GNAT 3.15p, GtkAda 2.2.0). AIDE is unique by its licence, its
integration and its seamless system integration :

    * All the tools needed are free, integrated and already configured
;
    * AIDE is immediately useable after a simple disk copy ;
    * No entry in the registry ;
    * No file in any system directory ;
    * No environment variables created or modified outside AIDE.
 
See detailed information on the web site :
http://stephane.rochebrune.org

Regards from France

-- 
Stephane Riviere
Oleron Island - France
http://stephane.rochebrune.org
OpenPgp Key <5fd6a1e6> available on the web site above

Re: GNAT on a multiboot computer

[Anders Wirzenius]

Adrien Plisson <aplisson-news@stochastique.net> writes:

> Anders Wirzenius wrote:
> > Tkanks, but I have not got any help from the registry.
> > These are from the "XP registry" (hardisk C:):
> > --------------------------------------------
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies] "GCC"="C:\\GNAT"
> > "MINGW32"="@GCC" "GNAT"="@GCC" "VERSION"="3.15p" "BINUTILS"="@GCC"
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\GNAT]
> > "ROOT"="C:\\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]
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT]
> > "Root"="c:\\mgnat"
> > [HKEY_LOCAL_MACHINE\SOFTWARE\Ada Core Technologies\MGNAT\Standard
> > Libraries] "DOTNET"="c:\\mgnat\\include"
> > ------------------------------------------------
> > There is of course nothing in the "WIN 2003 registry" (E:) Maybe I
> > could
> > copy the GNAT keys from XP to 2003?  Maybe the "ROOT"="C:\\GNAT" is
> > missing in 2003?
> 
> that what I was meaning... you can try to copy them from XP to 2003.
> but BEWARE OF THE GUID key !! it seems to relate to uninstall
> informations, but on my machine I can also find a reference to this
> GUID in the ARPCache (!?! why is it referenced here !?!)
> 
> try and see !
> 
> -- 
> rien

I tried and saw. :)

Success.
At least my small test program was linked and could be run successfully.
Thanks again.

I forgot to remove the GUID key, but will remove it from the 2003 registry.

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.

Anders

Re: GNAT on a multiboot computer

[Anders Wirzenius]

stephane@_delete_this_rochebrune.org (Stephane Riviere) writes:

> On Tue, 26 Oct 2004 07:03:27 GMT, Anders Wirzenius
> <anders@no.email.thanks.invalid> wrote:
> >Does anyone have a good advice on how to set up the
> >GNAT compiler system on a multiboot Windows computer?
> 
> You can use AIDE (Ada Instant Development Environment) for Windows
> (GNAT 3.15p, GtkAda 2.2.0). AIDE is unique by its licence, its
> integration and its seamless system integration :
> 
>     * All the tools needed are free, integrated and already configured
> ;
>     * AIDE is immediately useable after a simple disk copy ;
>     * No entry in the registry ;
>     * No file in any system directory ;
>     * No environment variables created or modified outside AIDE.
>  
> See detailed information on the web site :
> http://stephane.rochebrune.org
> 
> Regards from France
> 
> -- 
> Stephane Riviere
> Oleron Island - France
> http://stephane.rochebrune.org
> OpenPgp Key <5fd6a1e6> available on the web site above

Thank you. I try to find time to have a look at it. Presently my time is
spent on learning .NET for which I use the Win 2003 OS. My intention is
to get GNAT and MGNAT running on 2003 using the existent XP
installations.

Anders

Re: GNAT on a multiboot computer

[Adrien Plisson]

Anders Wirzenius wrote:
> I tried and saw. :)
> 
> Success.

cool !

> At least my small test program was linked and could be run successfully.
> Thanks again.
> 
> I forgot to remove the GUID key, but will remove it from the 2003 registry.

i don't think it will do any harm, so if it really works don't bother removing 
it...

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

-- 
rien

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

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
   c:\opt\sybase
   c:\opt\mysql

etc.

-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg

Re: GNAT on a multiboot computer

[Pascal Obry]

"Warren W. Gay VE3WWG" <ve3wwg@NoSPAM.cogeco.ca> writes:

> I have developed a fondness for C:\opt for non-cygwin software:

Same here !

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

Re: GNAT on a multiboot computer

[Martin Krischik]

Warren W. Gay VE3WWG wrote:

> 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
>    c:\opt\sybase
>    c:\opt\mysql

I prefer:

D:\cygwin\opt\gnat

etc.

Has two advantages:

  1) if you need to reinstall windows you cygwin on D: will not be destroyed
  2) within cygwin you can use shorter /opt instead of /cygdrive/c/opt

With Regards

Martin

-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com

Re: GNAT on a multiboot computer

[Anders Wirzenius]

"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]?
...?
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).

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

Re: GNAT on a multiboot computer

[Anders Wirzenius]

Martin Krischik <martin@krischik.com> writes:

> Warren W. Gay VE3WWG wrote:

> > I have developed a fondness for C:\opt for non-cygwin software:
> > 
> >    c:\opt\gnat
> >    c:\opt\sybase
> >    c:\opt\mysql
> 
> I prefer:
> 
> D:\cygwin\opt\gnat
> 
> etc.
> 
> Has two advantages:
> 
>   1) if you need to reinstall windows you cygwin on D: will not be destroyed
>   2) within cygwin you can use shorter /opt instead of /cygdrive/c/opt
> 

Nice.

Is your OS installed on C:?

Anders

Re: GNAT on a multiboot computer

[Adrien Plisson]

Warren W. Gay VE3WWG wrote:
>Has two advantages:
>
>  1) if you need to reinstall windows you cygwin on D: will not be destroyed

you can't assume that for any software installed on windows, and cygwin is no 
exception. most softwares write keys in the registry which you lose if you 
reinstall. those missing keys may render the software unusable (for cygwin, it 
seems all mount points are stored in the registry). only GPS is smart enough 
and don't need an installation.

i dream of a system which don't have any f****** conventions as "c:", nor any 
f****** weird locations as "Documents and Settings" or "/opt/usr/bin", and do 
not need any installation, ala Macintosh 10 years ago (copy where you want, run).

there is also a big incompatibility between unix software under cygwin and 
native software under windows: path incompatibilities, conventions 
incompatibilities, humor incompatibilities... all this gives me headaches when 
using cygwin: it took me 2 nights to configure and install Glade properl last 
week, and i still hadn't figure out how to make install PolyORB (configure 
script is buggy).

so, under Windows use the Windows way, under Unix use the Unix way, and don't 
even try to mix them or else you get a monster...

-- 
rien

Re: GNAT on a multiboot computer

[Martin Krischik]

Anders Wirzenius wrote:

> Martin Krischik <martin@krischik.com> writes:
> 
>> Warren W. Gay VE3WWG wrote:
> 
>> > I have developed a fondness for C:\opt for non-cygwin software:
>> > 
>> >    c:\opt\gnat
>> >    c:\opt\sybase
>> >    c:\opt\mysql
>> 
>> I prefer:
>> 
>> D:\cygwin\opt\gnat
>> 
>> etc.
>> 
>> Has two advantages:
>> 
>>   1) if you need to reinstall windows you cygwin on D: will not be
>>   destroyed 2) within cygwin you can use shorter /opt instead of
>>   /cygdrive/c/opt

> Nice.
> 
> Is your OS installed on C:?

Well, would you install Windows anywhere else? Honestly, there are *to* many
stupid programs around which have serious problems when Windows is anywhere
else then C:\Windows that it never crosses my mind to use anything else
then C:.

{On the other hand: I have never though twice when installing OS/2 on
D: ;-) }

With Regards

Martin 

-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com

Re: GNAT on a multiboot computer

[Anders Wirzenius]

Martin Krischik <martin@krischik.com> writes:

> Anders Wirzenius wrote:

> > 
> > Is your OS installed on C:?
> 
> Well, would you install Windows anywhere else? Honestly, there are *to* many
> stupid programs around which have serious problems when Windows is anywhere
> else then C:\Windows that it never crosses my mind to use anything else
> then C:.
> 
> {On the other hand: I have never though twice when installing OS/2 on
> D: ;-) }
> 


I didn't know whether you had a multiboot computer or not. Hence my
question.


Anders

Re: GNAT on a multiboot computer

[Hyman Rosen]

Martin Krischik wrote:
> Well, would you install Windows anywhere else? Honestly, there are *to* many
> stupid programs around which have serious problems when Windows is anywhere
> else then C:\Windows that it never crosses my mind to use anything else
> then C:.

I still maintain that the best favor Microsoft ever did for programs
(if not programmers) was to make the default installation directory
for programs be '\Program Files' on the root drive. That finally made
everyone deal properly with blanks in file and directory names, on
pain of looking ridiculous otherwise. Blanks had been permitted in
names for a long time, both in Windows and Unix, but most programs
handled them very badly.

Re: GNAT on a multiboot computer

[Martin Krischik]

Hyman Rosen wrote:

> Martin Krischik wrote:
>> Well, would you install Windows anywhere else? Honestly, there are *to*
>> many stupid programs around which have serious problems when Windows is
>> anywhere else then C:\Windows that it never crosses my mind to use
>> anything else then C:.
 
> I still maintain that the best favor Microsoft ever did for programs
> (if not programmers) was to make the default installation directory
> for programs be '\Program Files' on the root drive. That finally made
> everyone deal properly with blanks in file and directory names, on
> pain of looking ridiculous otherwise. Blanks had been permitted in
> names for a long time, both in Windows and Unix, but most programs
> handled them very badly.

Not in Germany. It's only \Programme here ;-). However I consider it a pain
in the bud - because the is no easy to access configuration option for it.
Well there is one, but not easy to access.

Of corse "Documents and Settings" is worse. I don't want my personal files,
my Desktop and profile to be on C: but moving "Documents and Settings" is
almost impossible.

With Regards

Martin

-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com

Re: GNAT on a multiboot computer

[Martin Krischik]

Anders Wirzenius wrote:

> Martin Krischik <martin@krischik.com> writes:
> 
>> Anders Wirzenius wrote:
> 
>> > 
>> > Is your OS installed on C:?
>> 
>> Well, would you install Windows anywhere else? Honestly, there are *to*
>> many stupid programs around which have serious problems when Windows is
>> anywhere else then C:\Windows that it never crosses my mind to use
>> anything else then C:.
>> 
>> {On the other hand: I have never though twice when installing OS/2 on
>> D: ;-) }

> I didn't know whether you had a multiboot computer or not. Hence my
> question.

Well I do have and I give C: to Windows. Mind you, I also own VMWare ;-)
which make a lot of things easier.

With Regards

Martin
-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com

Re: GNAT on a multiboot computer

[Pascal Obry]

Martin Krischik <martin@krischik.com> writes:

> I prefer:
> 
> D:\cygwin\opt\gnat

This is quite confusing as GNAT is not based on Cygwin!

Why not:

  d:\opt\gnat
  d:\opt\cygwin
  d:\opt\...

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

Re: GNAT on a multiboot computer

[Alex R. Mosteo]

Martin Krischik wrote:
> Hyman Rosen wrote:
> 
> 
>>Martin Krischik wrote:
>>
>>>Well, would you install Windows anywhere else? Honestly, there are *to*
>>>many stupid programs around which have serious problems when Windows is
>>>anywhere else then C:\Windows that it never crosses my mind to use
>>>anything else then C:.
> 
>  
> 
>>I still maintain that the best favor Microsoft ever did for programs
>>(if not programmers) was to make the default installation directory
>>for programs be '\Program Files' on the root drive. That finally made
>>everyone deal properly with blanks in file and directory names, on
>>pain of looking ridiculous otherwise. Blanks had been permitted in
>>names for a long time, both in Windows and Unix, but most programs
>>handled them very badly.
> 
> 
> Not in Germany. It's only \Programme here ;-). However I consider it a pain
> in the bud - because the is no easy to access configuration option for it.
> Well there is one, but not easy to access.

You lucky Germans. There must be a translator with some brains over 
there. We Spanish also got "Archivos de programa", which is a ridiculous 
expression for "programas" (then again, I think that "programs" instead 
of "program files" would have been much better).

Re: GNAT on a multiboot computer

[Adrien Plisson]

Martin Krischik wrote:
> Of corse "Documents and Settings" is worse. I don't want my personal files,
> my Desktop and profile to be on C: but moving "Documents and Settings" is
> almost impossible.

it is worst:
- "Documents and Settings" is kind of a black hole which mixes system 
configuration, application configuration and unrelated personnal files with no 
real hierarchy or convention. there is not a clear difference between 
"Application Data" and "Local Settings", and a redundancy between "Application 
Data" and "Local Settings\Application Data".
- It has been designed as the "home" directory of a user (if unsure, type "set 
HOME" at a command prompt) but it is not directly accessible from the desktop 
by default, only "My Documents" is. since i cannot categorize all the files i 
create on a computer as "documents", some are configurations, some are 
programs, some are just garbage. so i don't and i will never use this folder. 
(plus, i find the name totally dumb). so, for a home directory, it is not very 
comfortable, not the kind of home i would like to live in.

going further: Microsoft could have pushed the "My" principle farther:
"c:\My Programs", "c:\My Home\My Documents", but this have no meaning on a 
truly multiuser station: "My Computer" can then mean "The Computer seldomly 
used by Joe", "The Computer often mis-used by Sally" or even "The Computer 
owned by your Boss".

-- 
rien

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

Adrien Plisson wrote:
> Warren W. Gay VE3WWG wrote:
> 
>> Has two advantages:
>>
>>  1) if you need to reinstall windows you cygwin on D: will not be 
>> destroyed

The attribution above is not correct - I did not say this.

Warren.

> 
> 
> you can't assume that for any software installed on windows, and cygwin 
> is no exception. most softwares write keys in the registry which you 
> lose if you reinstall. those missing keys may render the software 
> unusable (for cygwin, it seems all mount points are stored in the 
> registry). only GPS is smart enough and don't need an installation.
> 
> i dream of a system which don't have any f****** conventions as "c:", 
> nor any f****** weird locations as "Documents and Settings" or 
> "/opt/usr/bin", and do not need any installation, ala Macintosh 10 years 
> ago (copy where you want, run).
> 
> there is also a big incompatibility between unix software under cygwin 
> and native software under windows: path incompatibilities, conventions 
> incompatibilities, humor incompatibilities... all this gives me 
> headaches when using cygwin: it took me 2 nights to configure and 
> install Glade properl last week, and i still hadn't figure out how to 
> make install PolyORB (configure script is buggy).
> 
> so, under Windows use the Windows way, under Unix use the Unix way, and 
> don't even try to mix them or else you get a monster...
> 


-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

Martin Krischik wrote:

> Warren W. Gay VE3WWG wrote:
> 
> 
>>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
>>   c:\opt\sybase
>>   c:\opt\mysql
> 
> 
> I prefer:
> 
> D:\cygwin\opt\gnat

I support the idea of a separate drive (D:) for the reasons you gave.
However, in my case, I am using a company laptop, so I am loath to
change the partitioning on it (any spare disk will be used for Linux,
if possible - TBD).

I disagree with putting non-Cygwin software in the cygwin's /opt
hierarchy, however (assuming your D:\cygwin\opt maps to
/opt in your Cygwin).

Non-Cygwin programs have a different environment requirement (for
example the GNAT supplied make is different than cygwin's). While
there is nothing to stop you from putting them in the same directories,
I prefer to keep the two "worlds" apart.


Warren.

> 
> etc.
> 
> Has two advantages:
> 
>   1) if you need to reinstall windows you cygwin on D: will not be destroyed
>   2) within cygwin you can use shorter /opt instead of /cygdrive/c/opt
> 
> With Regards
> 
> Martin
> 


-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg

Re: Directory Names (was: GNAT on a multiboot computer)

[Warren W. Gay VE3WWG]

Hyman Rosen wrote:

> Martin Krischik wrote:
> 
>> Well, would you install Windows anywhere else? Honestly, there are 
>> *to* many
>> stupid programs around which have serious problems when Windows is 
>> anywhere
>> else then C:\Windows that it never crosses my mind to use anything else
>> then C:.
> 
> I still maintain that the best favor Microsoft ever did for programs
> (if not programmers) was to make the default installation directory
> for programs be '\Program Files' on the root drive. That finally made
> everyone deal properly with blanks in file and directory names, on
> pain of looking ridiculous otherwise. Blanks had been permitted in
> names for a long time, both in Windows and Unix, but most programs
> handled them very badly.

How far do you want to take that argument? You can put
semicolons in directory names too (Windows). But then, how will that
work with the Windows PATH variable? Good luck making that work!

The same thing happens in UNIX: You can put colons in directory
names, but this is guaranteed to give you trouble in the shell's
PATH variable.

So it still comes down to conventions and "practical use".

While I always believe in writing robust shell scripts, I still
loath blanks in directory names. C:\Programs would have
been sufficient in Windows IMHO.

-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg

Re: GNAT on a multiboot computer

[Björn Persson]

Hyman Rosen wrote:

> I still maintain that the best favor Microsoft ever did for programs
> (if not programmers) was to make the default installation directory
> for programs be '\Program Files' on the root drive. That finally made
> everyone deal properly with blanks in file and directory names, on
> pain of looking ridiculous otherwise.

Not everyone. :-) The Swedish name of that directory is "Program", and a 
problem that often occurs in Sweden is that C:\Program is opened every 
time you log in. This happens when a program has installed an autostart 
command but made two errors: It assumed that the directory for programs 
is always C:\Program Files, and it didn't quote the command properly.

-- 
Björn Persson                              PGP key A88682FD
                    omb jor ers @sv ge.
                    r o.b n.p son eri nu

Re: GNAT on a multiboot computer

[Larry Kilgallen]

In article <41820f69$0$7073$ba620e4c@news.skynet.be>, Adrien Plisson <aplisson-news@stochastique.net> writes:

> i dream of a system which don't have any f****** conventions as "c:", nor any 
> f****** weird locations as "Documents and Settings" or "/opt/usr/bin", and do 
> not need any installation, ala Macintosh 10 years ago (copy where you want, run).

Some of this certainly pertains to elaborate OS mechanisms to which
application developers choose to conform.

On VMS, for example, copying a program to a particular location and
then using the RUN command works fine.  But...

	If the program uses a shareable image in concert with
	other programs, that shareable image either must be
	in SYS$SHARE or must have a logical name defined.

	If the program uses a separate message image in order
	to support internationalization, that message image must
	be in SYS$MESSAGE or must have a logical name defined.

	If the program documentation supports the DCL command
	HELP/MESSAGE an existing logical name must be modified
	by the system manager.

	If the program is to be invoked by its own native command
	like LJK/SECURITY SHOW ASSESSMENT rather than RUN, the
	SET COMMAND command must be used to establish that command.

And of course any of those steps which will affect other users of the
system must be done by someone with system management privilege.

You can still do the "copy-run" approach or even RUN directly
from the source location of the program, but life gets more
complicated when multiuser environments are involved.  In fact,
for the best security no user should have the right to execute
any program they provided, since they might be inappropriately
trusting the source of that program !

Re: GNAT on a multiboot computer

[Martin Krischik]

Pascal Obry wrote:

> 
> Martin Krischik <martin@krischik.com> writes:
> 
>> I prefer:
>> 
>> D:\cygwin\opt\gnat
> 
> This is quite confusing as GNAT is not based on Cygwin!

There is a cygwin based GNAT as well. And - good news - the gcc 3.4.x does
actually compile with the current cygwin gcc 3.3.x. Just do the same steps
as you would for linux.

Only problem: the cygwin GNAT can't create DLLs.

My mingw based GNAT is, of corse, in D:\mingw.

With Regards

Martin

-- 
mailto://krischik@users.sourceforge.net
http://www.ada.krischik.com

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

Pascal Obry wrote:
> Martin Krischik <martin@krischik.com> writes:
> 
> 
>>I prefer:
>>
>>D:\cygwin\opt\gnat
> 
> 
> This is quite confusing as GNAT is not based on Cygwin!
> 
> Why not:
> 
>   d:\opt\gnat
>   d:\opt\cygwin
>   d:\opt\...
> 
> Pascal.
> 

I made that point earlier this morning myself. While you
can lump them together, I prefer to keep them separate since
the non-cygwin and cygwin environments differ considerably.

-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

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

Re: GNAT on a multiboot computer

[Adrien Plisson]

Warren W. Gay VE3WWG wrote:
(i hope i don't misattribute your post again... sorry)

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

even when using pathnames with spaces, act's own install is smart enough 
to keep only 8.3 pathnames, so you don't have to worry about that.

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

false: the registry is not shared between multiple Windows installed on 
the same machine (fortunately, or it will be a real mess to have 
multiple WIndows on the same machine). so you just have to register GNAT 
once for each installation of Windows then use it at will. this is much 
simpler !!

> (I am sure there are other ways this can
> be automated).

not needed: see above...

-- 
rien

Re: GNAT on a multiboot computer

[Pascal Obry]

Martin Krischik <martin@krischik.com> writes:

> Only problem: the cygwin GNAT can't create DLLs.

And Cygwin GNAT does not support tasking AFAIK. At least that was the case
last time I looked at it. It is also the case that Cygwin based programs are a
bit slower and required an external DLL (cygwin.dll), that's why I prefer the
*native* (proceduces programs that do not require external DLL, it runs on any
Windows flavor) MingW based compilers.

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.org
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

Re: GNAT on a multiboot computer

[Stephane Riviere]

>i dream of a system which don't have any f****** conventions as "c:", nor any 
>f****** weird locations as "Documents and Settings" or "/opt/usr/bin", and do 
>not need any installation, ala Macintosh 10 years ago (copy where you want, run).

I fully agree with you. This is why I've created AIDE. For the Windows
path, all your needs may be found in it (mingw based for real windows
usefullness). AIDE obviously must be improve in many ways, (help
welcome). English manual is underway but the whole is already tested
and usable.

>so, under Windows use the Windows way, under Unix use the Unix way, and don't 
>even try to mix them or else you get a monster...

AIDE is definitly not like that : simple directories hierarchy,
emacs/glide (preferred) or gps or console based (with the simpler fte
editor) : no special requirements or imposed softwares.

You can also reproduce the AIDE environment in any other platform as
all the softwares used in AIDE are free and multi-platform (it was one
of the design objective).

-- 
Stephane Riviere
Oleron Island - France
http://stephane.rochebrune.org
OpenPgp Key <5fd6a1e6> available on the web site above

Re: GNAT on a multiboot computer

[Anders Wirzenius]

Adrien Plisson <aplisson-news@stochastique.net> writes:

> Warren W. Gay VE3WWG wrote:
> (i hope i don't misattribute your post again... sorry)
> 
> > 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.
> 
> false: the registry is not shared between multiple Windows installed
> on the same machine (fortunately, or it will be a real mess to have
> multiple WIndows on the same machine). so you just have to register
> GNAT once for each installation of Windows then use it at will. this
> is much simpler !!
> 

Correct. Not shared.

I got GNAT to work by: 
- booting into Win XP 
- exporting the ACT registry settings (which contained references to C:)
- saving the reg-file
- booting into Win 2003
- importing the reg-file into 2003 registry (on E:)
- inserting C:\GNAT ... at the beginning of the path variable

I was then just curious whether my manual changes to the environment
were similar to what you get when you install GNAT in another directory
than the default (C:\GNAT...).

Case closed, thanks to all.

Anders

Re: GNAT on a multiboot computer

[Warren W. Gay VE3WWG]

Adrien Plisson wrote:
> Warren W. Gay VE3WWG wrote:
> (i hope i don't misattribute your post again... sorry)
> 
>> ACT's own install program lets you choose - so just choose away! Just
>> avoid blanks in the directory names. 8-)
> 
> 
> even when using pathnames with spaces, act's own install is smart enough 
> to keep only 8.3 pathnames, so you don't have to worry about that.
> 
>> 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.
> 
> 
> false: the registry is not shared between multiple Windows installed on 

They need not be shared. My point was that you can bring over the
settings (modified as required). They are real easy to import.

-- 
Warren W. Gay VE3WWG
http://home.cogeco.ca/~ve3wwg