X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 16 Jun 2008 23:41:52 -0400 From: Mike Mueller To: cygwin@cygwin.com Subject: Cygwin app not receiving modified PATH env var Message-ID: <20080617034152.GD7632@samus.subfocal.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hey all, I have a program (native win32) that is capable of launching sub-processes, using apr (apache portable runtime), which is essentially a wrapper around CreateProcess in the Windows API. My program creates a modified environment (changes the PATH env var), and passes this new environment to CreateProcess. When I run a native Windows program, for example, a .bat script that says "echo %PATH%", I see the correctly modified PATH env var. When I run a Cygwin program, the PATH is the original unmodified path (rephrased in cygwin format), maybe inherited from the parent process? The modified PATH being passed to CreateProcess is not discovered by the Cygwin app. I would've expected the two to behave the same in this situation. Has anyone done anything like this before? Is there a known issue here, or is this a new bug? Workarounds? Thanks, Mike -- Mike Mueller mike@subfocal.net -- 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/