Re: GWorkspace porting troubles

[Enrico Sersale]

On Mon, 29 Oct 2001 LHelldorf@kabel.de wrote:

> At first I want to thank you all for your help. I also think it is the
> right idea to put the vast majority of the changes in a compatibility
> header, whether it will be called MacOSXCompat.h or GNUstep.h.
>
> My way to go was to create a file called GNUstep.h from your input
> (I've choosen to take the best of both efforts) and to include this
> headerfile in every source file (.m) I found. Here is my version of
> GNUstep.h:
>
> ...

I've included this version of the file in all the sources.

> GWorkspace.m: In function `+[GWorkspace gworkspace]':
> GWorkspace.m:92: `gnustep_global_lock' undeclared (first use in this
> function)
> GWorkspace.m:92: (Each undeclared identifier is reported only once
>
> ...

Also this was changed.

Later I'll put a new release on www.gnustep.it.