Re: gnustep-base on windows

[Alex Perez]

Marko, see below

Marko Riedel wrote:
> Hi all,
>
> I downloaded the installer from 
>
>   http://ftpmain.gnustep.org/pub/gnustep/binaries/windows/
>
> and everything compiled without even the slightest hitch!
>
> Congratulations!
>
> Next I tried to compile the permutation enumeration recipe from my GNUstep
> cookbook. Unbelievable! The program runs and its output is correct.
>
> Good work, people!
>
> I do have one problem, however. My profile does not reside on the local
> hard drive, but on a file server. It seems GNUstep cannot handle network
> drives yet. First it complained about not being able to create
> GNUstep/Defaults, so I created them manually. This gives the following
> trace.
>
> 2005-02-04 16:35:07.000 permenum.exe[936] Failed to create lock directory
> '~@myserver/profile/riedel/GNUstep/Defaults/.GNUstepDefaults.lck' - Die
> Syntax für den Dateinamen, Verzeichnisnamen oder die
> Datenträgerbezeichnung ist falsch.
>
> 2005-02-04 16:35:07.000 permenum.exe[936] Failed to lock user defaults
> database even after breaking old locks!
> 2005-02-04 16:35:07.000 permenum.exe[936] WARNING - unable to create
> shared user defaults!
> 2005-02-04 16:34:51.000 permenum.exe[936] (b, c, a)
> 2005-02-04 16:35:07.000 permenum.exe[936] (c, b, a)
> 2005-02-04 16:35:07.000 permenum.exe[936] (c, a, b)
> 2005-02-04 16:35:07.000 permenum.exe[936] (a, c, b)
> 2005-02-04 16:35:07.000 permenum.exe[936] (b, a, c)
> 2005-02-04 16:35:07.000 permenum.exe[936] (a, b, c)
> 2005-02-04 16:35:07.000 permenum.exe[936] total: 6
> 2005-02-04 16:35:07.000 permenum.exe[936] ((b, c, a), (c, b, a), (c, a,
> b), (a, c, b), (b, a, c), (a, b, c))
> The file 'c:\GNUstep\System\.GNUsteprc' is writable by someone other than
> its owner.
> Ignoring it.
> The file 'c:\GNUstep\System\.GNUsteprc' is writable by someone other than
> its owner.
> Ignoring it.
>
> The translation of the German is: "the syntax used in the
> file/directory/medium is wrong."
>
> Can you help me out here? Additional question: what's the status of
> gnustep-gui on windows?

The problem is actually more of a mingw32-path-mangling problem than a 
problem with GNUstep, but we will likely have to modify GNUstep to 
accept path formats under win32 that it would likely otherwise reject. 
Is the network volume you're trying to run GNUstep from a mapped drive 
under windows? It is connected via SMB? NFS? Did you try using the UNC 
path to the network resource? (The UNC format is \\server\path\to\file.txt)

I have taken an active interestin in improving GNUstep win32 support, so 
I will do some of my own testing, but I am also interested in your results.

Cheers
Alex Perez