Re: patch to common.make for cygwin paths

[Nicola Pero]

Sorry for answering late - being busy at the moment - thanks for reporting
the problem - the obvious fix is to move the check after config.make has
been included ... no particular reason why it should go before.

Can you try moving the check from where it is to just after 

#
# Get the config information
#
include $(GNUSTEP_MAKEFILES)/$(GNUSTEP_TARGET_DIR)/config.make

in common.make, and let me know if it works.  If it does, I'll apply this
change to CVS.

> Hi,
> 
> Hmmm, I'm still getting the warnings after updating from
> CVS. What's going on is that $(GNUSTEP_TARGET_OS) has not
> been set by the time it's being checked in common.make. I
> tested setting GNUSTEP_TARGET_OS from the command line
> before doing the "make target=i386-mingw32" and that did the
> right thing.
> 
> But - shouldn't the "target" I specify in  "make
> target=i386-mingw32" become the internal GNUSTEP_TARGET_OS
> variable? Or perhaps that only happens in a subsequent part
> of the makefile system?
> 
> Cheers,
> Stephen
> 
> 
> On Tue, 6 Nov 2001 02:50:10 +0000 (GMT)
>  Nicola Pero <n.pero@mi.flashnet.it> wrote:
> > 
> > > I get the bogus warning when compiling on Windows and
> > it really is 
> > > annoying/confusing. So it would be nice to fix it. I
> > guess at the risk 
> > > of expanding the code infinitely, we could do:
> > > 
> > > ifeq ($(findstring mingw, $(GNUSTEP_TARGET_OS)), mingw)
> > >   ...windows specific check
> > > else
> > >   ...unix specific check
> > > endif
> > > 
> > > (also including cygwin)
> > 
> > Ok - I committed something of this kind - it didn't break
> > unix :-) - let
> > me know if it fixes the spurious warning on windows or
> > not.
> > 
> 
> 
> _______________________________________________
> Bug-gnustep mailing list
> Bug-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-gnustep
>