X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fI5cLL3JjiN14LxV
	mq3ETp0hzmO1FFEzPkIZa5wlqWiTNKgE0epTY0vFyDzy3pQWwp9BCldChJA6JUip
	D+5tdh0GLzeigwu8ioHUZqy4SX9CESm7Bppbb3z/DJcd7vnOLl0G/llefpV0o3xD
	QnQGTbhJyJ0XN2ds4ATf6YTMi6U=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=W4FwMV5lh+vxYc0Exxz1Z7
	RI7n8=; b=pMA2/rbC4WEumZ/kxJxt/jsGYjruM3JxCIrJ0VQaJFSVxJgLKDoYgA
	Qd3f/987HEIFHsoowW+FmnKRTBKJrGeMoVbLd6uhCDxVSVLTjyVmJXmme12w/TeJ
	GzHng+rwJoWCwwAMUpZkCi8VKGD6Bs5pU+9IxSHESiQYmsqEWYUfc=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173025pub.verizon.net
Message-id:	<5371173B.9080509@cygwin.com>
Date:	Mon, 12 May 2014 14:47:23 -0400
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: How do start a cygwin shell session from a script ?
References:	<CAPbWNKGufbzvGCQd4u4e3nNp5OteAWM=C7=AgE1z-UVoN6XzjA AT mail DOT gmail DOT com>
In-reply-to:	<CAPbWNKGufbzvGCQd4u4e3nNp5OteAWM=C7=AgE1z-UVoN6XzjA@mail.gmail.com>

On 05/12/2014 06:12 AM, Timothy Madden wrote:
> Hello
>
> I have a CMake build script for my application, that among other
> things tries to build libvpx (open-source video codec, see
> webmproject.org).
>
> libvpx library v1.3.0 compiles fine by hand when I open a cygwin
> terminal from the Windows start menu and type in the needed
> `configure`; `make` and `make install` commands.
>
> But when I try to invoke the cygwin shell from my build script, to run
> the same 3 commands with the -lc option to sh.exe (same command line),
> something happens and the build commands no longer work like in the
> real mintty terminal. Then my build fails.
>
> I believe there is something in the cygwin shell session or
> environment that I do not know how to set right when invoking
> $(CYGWIN_DIR)/bin/sh from my CMake script.
>
> Is there a way for me to start a cygwin shell session from the build
> script, that is identical to the one that opens in the mintty terminal
> from the start menu, and run some commands there ?
>
> I checked the environment variables and umask in the mintty terminal
> and in a /bin/sh session that I launch, they are the same in both
> cases. I tried using /bin/sh, /bin/bash, /bin/dash, with both --login
> and -c options. But the automated build always fails, and the manual
> build works.

What's the error and from where?

I think you are on the right track to look at environment differences.
If you're sure there are no longer any differences between the sessions
invoked through CMake and manually, I'd suspect something surrounding
CMake.  Do you have the same problem using Cygwin's CMake?


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

- Raw text -