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: Mon, 13 Mar 2000 13:02:09 +0430 (GMT+04:30)
From: jens AT uniweb DOT se
Subject: Re: The implementation of popen().
To: cygwin AT sourceware DOT cygnus DOT com
Cc: cgf AT cygnus DOT com
Message-id: <464949610.952936329429.JavaMail.root@colin.uniweb.se>
MIME-version: 1.0
X-Mailer: Sun(TM) Web Access 1.2
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

 Hi,

 I'm not looking to 'take' the code. What I was looking for was some information about how it was done in cygwin and if someone know if this was a simple solution. What I want is for stdin/stdout to work when I use popen() in multiple steps using the popen() in msvcrt.dll. And the reason for asking here was that it seem to work in cygwin. So I thought maybe the knowledge was here. But maybe I should ask at the cygwin-developer list instead. I just thought that I should not start by desturbing them.

 Jens Yllman

>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
>
>

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