freetype-devel
[Top][All Lists]
Advanced

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

Re: [Devel] FT2 + cygwin


From: David Turner
Subject: Re: [Devel] FT2 + cygwin
Date: Tue, 12 Dec 2000 20:03:14 +0100

Hi Karsten,

> 
> Generally, unix configure should work on UWIN and Cygwin without any
> changes. But the detect.mk files have to be changed.
> 
> unix/detect.mk checks for /sbin/init, which is not there on Cygwin and on
> UWIN. We would have to check for something "unixish" which is there on both
> systems. There are other unix emulations for Windows (e.g. NuTcracker), but
> I have only Cygwin and UWIN available, so I can't speak for them.
> 
> Maybe checking for /usr/bin is sufficient for detecting unix (like) system?
> 
> We also have to prevent DOS and Win32 detection.
>
I think that detecting Cygwin is _not_ so important. After all, using a
specific setup target, as in "make setup cygwin", should be enough when
run from the Windows command shell.

What could be fun however is to auto-detect Cygwin from the Bash
shell on Win32 though.. and this is certainly easy to do..
 
> DOS/Win9x/ME detection is done by checking for the COMSPEC environment
> variable,
> NT detection by checking $OS == Windows_NT.
> 
> I have a NT 4.0 machine and OS is Windows_NT on Cygwin and on UWIN, whereas
> COMSPEC is only set to C:\WINNT\system32\cmd.exe on Cygwin. On UWIN it is
> not set.
> 
> So what should we check for?
> I'd volunteer for doing the necessary changes, although I have a lot of
> other things to do at the moment (but that's makefiles, too, so not very
> different).
> 

Again, I don't see why we should try to automatically detect Cygwin
on Win32 systems. It seems that this greatly simplifies the problem.

As to UWIN, NutCracker, etc.., I don't know enough about them to tell

Regards,

- David





reply via email to

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