This is the mail archive of the cygwin mailing list for the Cygwin project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 10/24/2014 09:19 AM, John Wiersba wrote: > I thought that all (or virtually all) cygwin-supplied programs that start > other programs use the cygwin1.dll execve(2) emulation to start them, because > the execve emulation can be used to start *both* cygwin programs and windows > native programs. Or at least it seems that way to me. > > Is there be in drawback to having run.exe start its target program using > the execve emulation in cygwin1.dll, rather than using a Windows call to > start the target executable? run.exe is special. In order to hide consoles, it MUST use native windows API instead of cygwin1.dll calls. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |