On Wed, Jun 18, 2008 at 12:30:22PM +0200, Corinna Vinschen wrote:
> As I said, PATH is fetched with GetEnvironmentStrings from the env like
> every other environment var, if the Cygwin app has been started by a
> native parent. It's just massaged into a POSIX path afterwards.
> There's no magic in
Thanks for the replies, Corinna.
> > A little further info. It looks like apr detects a unicode environment,
> > so ultimately is calling CreateProcessW (not CreateProcessA).
>
> How do you pass your unicode env? Do you set the CREATE_UNICODE_ENVIRONMENT
> flag?
I get a snapshot of the current
On Tue, Jun 17, 2008 at 09:05:36PM -0400, Mike Mueller wrote:
> On Mon, Jun 16, 2008 at 11:41:52PM -0400, Mike Mueller wrote:
> > I have a program (native win32) that is capable of launching
> > sub-processes, using apr (apache portable runtime), which is essentially
>
On Mon, Jun 16, 2008 at 11:41:52PM -0400, Mike Mueller wrote:
> 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
ocess?
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
5 matches
Mail list logo
