Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Sat, 6 Jan 2001 12:37:32 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Porting Cygwin
Message-ID: <20010106123732.A13687@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3A5741F9 DOT 8951 DOT 320B753B AT localhost> <00d001c077fa$895c97d0$6701a8c0 AT dafcoix6jzgi66> <000b01c077fe$e48824e0$9865fea9 AT timayum4srqln4> <20010106115438 DOT B13257 AT redhat DOT com> <00fb01c07804$d61de6a0$6701a8c0 AT dafcoix6jzgi66>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <00fb01c07804$d61de6a0$6701a8c0@dafcoix6jzgi66>; from dfeustel@mindspring.com on Sat, Jan 06, 2001 at 12:19:32PM -0500

On Sat, Jan 06, 2001 at 12:19:32PM -0500, David Feustel wrote:
>>On Sat, Jan 06, 2001 at 08:36:57AM -0800, Tim Prince wrote:
>>>>Now, am I correct in my assumption that porting the cygwin dll to WinCE
>>>>will let me compile, GCC source and the link/run it using the EVT c
>>>>compiler with not a whole lot of editing?
>>>>
>>>>If so, where can I find the makefile for the cygwin dll?
>>>
>>>Does CE support fork?  That has been missing from certain Windows
>>>variants.  gcc usually has to be ported by starting with a cross build,
>>>using a working gcc, e.g.  on linux.
>>
>>Fork is actually missing from every version of Windows.  Or rather, the
>>POSIX layer on Windows NT supports it but cygwin doesn't use that.
>>
>>Cygwin has always rolled its own version of fork.
>>
>>Porting cygwin to Windows CE will be a nearly impossible task,
>>especially if you (Dave) are having problems just locating subscribing
>>to the mailing list and finding the Makefile.  This indicates to me
>>that you probably are not fully aware of the amount of effort required.
>>
>>The subset of the Windows API that is available for Windows CE is not
>>sufficient to get cygwin working.  The biggest problem is that there is
>>no equivalent to the Windows console.
>
>WinCE 2.11 has a console window.  I am using it in my ports of Teco and
>Snobol4 to my Jornada 820.  Teco is essentially done.  Snobol4 runs but
>needs work.  I have a Windows 2000 version running from essentially the
>same codebase which is helping me figure out what should be happening
>with Snobol on my Jornada.

That may be but I'm pretty certain that actual console I/O is not supported
by WinCE, e.g., AFAIK, you can't open CONIN$.

Besides the console operations, there are also other primitives that are
missing in Windows CE which Cygwin relies on.

Then, of course, there is the amount of memory that Cygwin will use.  Memory
is precious on hand helds.  Even if you got cygwin ported, I'm not sure how
much additional memory would be available for the application.

Btw, I neglected to respond to this:

>>>>Now, am I correct in my assumption that porting the cygwin dll to WinCE
>>>>will let me compile, GCC source and the link/run it using the EVT c
>>>>compiler with not a whole lot of editing?

I don't know what EVT c might be, but building Cygwin requires a recent
gcc compiler.  It's possible that you can use another compiler/linker to
use cygwin header files and libraries for building an application but
I wouldn't be surprised if there are problems there too.

cgf

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple