Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <66F336FF8FD0484B943E0CF48D923C2C053680D4@CSCEX04>
From: Alexander Enchevich <Alexander DOT Enchevich AT creo DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: AC_CYGWIN? 
Date: Wed, 11 Jun 2003 09:59:05 -0700
MIME-Version: 1.0
Content-Type: text/plain

> Note, though, that there is absolutely no problem with the filename 
> ".mumbleinit" on Cygwin (I just did a `touch .mumbleinit` to make sure)

On Cygwin there isn't but on "Win" there is - try copying/renaming an
existing file to something like .filename in Explorer (I tried it on Win2K).
You will get an err. message informing you that "You must type a filename"
:)

-----Original Message-----
From: Ronald Landheer-Cieslak [mailto:ronald AT landheer DOT com]
Sent: Wednesday, June 11, 2003 1:17 AM
To: Alexander Enchevich
Cc: cygwin AT cygwin DOT com
Subject: RE: AC_CYGWIN? 


Note, though, that there is absolutely no problem with the filename 
".mumbleinit" on Cygwin (I just did a `touch .mumbleinit` to make sure)

In fact, there are less and less reasons to distinguish Cygwin from *NIX 
platforms. (Thanks to the core developers and various contributers for 
that!)

rlc

On Tue, 10 Jun 2003, Alexander Enchevich wrote:

> Thanks for the tip Max, I looked in 'info autoconf' and found this 
> 
> =========info autoconf===========
> If you want to base a decision on the system where your program 
> will be run, make sure you use the `$host' variable, as in the 
> following excerpt:
> 
>      case $host in
>        *-*-msdos* | *-*-go32* | *-*-mingw32* | *-*-cygwin* | *-*-windows*)
>          MUMBLE_INIT="mumble.ini"
>          ;;
>        *)
>          MUMBLE_INIT=".mumbleinit"
>          ;;
>      esac
>      AC_SUBST([MUMBLE_INIT])
> =========info autoconf===========
> 
> So I guess that's all I need...
> 
> >Of course, checking for a platform kind of goes against the whole
> >feature-not-platform tests ideal of autoconf.
> 
> I have to! :/ The code is already there, full of defines (#ifdef WIN32 and
> #ifdef APPLE) and it was not written with Linux or cygwin in mind and now
it
> has to be converted, so... 
> 
> -----Original Message-----
> From: Max Bowsher [mailto:maxb AT ukf DOT net]
> Sent: Tuesday, June 10, 2003 5:16 PM
> To: Alexander Enchevich; cygwin AT cygwin DOT com
> Subject: Re: AC_CYGWIN? 
> 
> 
> Alexander Enchevich wrote:
> > Hi
> >
> > What's the proper way to check if I am compiling on a cygwin system from
> > within an autoconf configure.in script?
> 
> >From the subject, you clearly already have an idea. If you check the
> autoconf docs, they will tell you that that macro is obsolete, and tell
you
> how you should be doing it.
> 
> Of course, checking for a platform kind of goes against the whole
> feature-not-platform tests ideal of autoconf.
> 
> 
> Max.
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/