Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 10 Mar 2000 11:50:57 -0500
From: Chris Faylor <cgf AT cygnus DOT com>
To: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Cc: Jens Yllman <jens AT uniweb DOT se>, cygwin AT sourceware DOT cygnus DOT com
Subject: Re: The implementation of popen().
Message-ID: <20000310115057.A7903@cygnus.com>
Reply-To: cygwin AT sourceware DOT cygnus DOT com
Mail-Followup-To: Chris Faylor <cgf AT cygnus DOT com>,
	Earnie Boyd <earnie_boyd AT yahoo DOT com>, Jens Yllman <jens AT uniweb DOT se>,
	cygwin AT sourceware DOT cygnus DOT com
References: <20000310144518 DOT 1453 DOT qmail AT web108 DOT yahoomail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.8i
In-Reply-To: <20000310144518.1453.qmail@web108.yahoomail.com>; from earnie_boyd@yahoo.com on Fri, Mar 10, 2000 at 06:45:18AM -0800

On Fri, Mar 10, 2000 at 06:45:18AM -0800, Earnie Boyd wrote:
>--- Jens Yllman <jens AT uniweb DOT se> wrote:
>>  It is strange how many answers came to this thread as soon as someone
>> found something amusing in the text. What I meant was that popen() is
>> depending on for instance fork(). And fork() is depending on some other
>> functions. So I did not see any easy way to just take that code and try
>> to use it in my code. And I did not at once see if there were a simple
>> solutions to my problem. So that is why I asked here to see if anybody
>> know something about this.
>> 
>
>Your question isn't related to using Cygwin, it is related to incorporating the
>Cygwin source code into yours statically and that is off topic for this list. 
>As far as I know, no one has yet taken the time to build Cygwin statically so
>you're on your own in getting using the pieces and parts of the code into
>yours.

Thank you for clarifying this, Earnie.

Let me just reiterate that there are licensing issues if you attempt this
route, too.  If you link in cygwin pieces, your program will become
GPLed.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com