[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNUstep under mingw

From: Nicola Pero
Subject: Re: GNUstep under mingw
Date: Fri, 8 Mar 2002 12:00:37 +0000 (GMT)

>  >>GNUSTEP_SYSTEM_ROOT/Tools directory. For this to work also the
>  >>environment variable GNUSTEP_TARGET_OS has to be set to
>  >>mingw32, which
>  >>is not mentioned in the README.mingw.
>  >>
>  >
>  > I think it says to use
>  >
>  > make target=i386-mingw32,
>  >
>  > which should work also
>  >
> Yes it does say the following:
> If you get tired of typing  "target=i386-mingw32" all the time, then before
> you exec the GNUstep.sh script, just set the GNUSTEP_HOST:
>    export GNUSTEP_HOST=i586-pc-mingw32
>    . $GNUSTEP_SYSTEM_ROOT/Makefiles/GNUstep.sh
> And a simple mind, as I am one might think after that the setting
> GNUSTEP_HOST would be equivalent to supplying target=XX which it is not.

I'm not sure what the problem is.  If you have a better way of writing the
text, send a patch with an explanation of why the change.  I love patches.  


I know nothing of Windows, but looking at the text, it always says to use
'make target=i386-mingw32'.

I understand the text about GNUSTEP_HOST meaning that setting GNUSTEP_HOST
gives you the same effect - in this particular case - as using make
target=xxx, not that it is equivalent in all cases.  I don't know if it is
correct that it gives the same effect.  It certainly causes
GNUSTEP_TARGET_XXX to be set correctly - but it - theoretically - might
cause problems because GNUSTEP_HOST has been hacked to be different from
the actual host environment ... I don't know.  Is that your problem ?

target=xxx is used by gnustep-make to set up the GNUSTEP_TARGET_XXX
variables.  That is normally used when cross-compiling.  For some reason I
don't know, it seems like on windows people are cross-compiling from
cygwin to mingw32 I think.

Anyway - the mingw readme says very clearly that it is all experimental -
if you find that some things don't work, please try to figure out
precisely what is wrong, and why, and exactly what could be done to make
it better, then send a detailed patch and improvement suggestion.

I'm very willing to listen to your problems and help you fix things which
don't work (and I'm sure Richard and Adam are as well) - but I don't use
Windows myself (and Richard and Adam don't seem to have encountered your
problems - but different ones) and unless you provide me with enough
input, I can't really help you.

I'm not surprised you found problems and I think there are lot of things
to fix still.  Both Adam and Richard - and anyone trying the brave
operation - found a lot of problems when they did it, so it's just quite
normal that you find problems as well.  You just need to investigate each
of them carefully, so that we fix them.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]