See spawn_async_with_pipes for a full description; this function simply calls the spawn_async_with_pipes without any pipes.
You should call close_pid on the returned child process reference when you don't need it any more.
If you are writing a GTK+ application, and the program you are spawning is a graphical application, too, then you may want to use
gdk_spawn_on_screen instead to ensure that the spawned program opens its windows on the right screen.
Note that the returned child_pid on Windows is a handle to the child process and not its identifier. Process handles and
process identifiers are different concepts on Windows.
| working_directory |
child's current working directory, or null to inherit parent's |
| argv |
child's argument vector |
| envp |
child's environment, or null to inherit parent's |
| child_setup |
function to run in the child just before |
| child_pid |
return location for child process reference, or null |
| flags |
flags from SpawnFlags |
| user_data |
user data for |
|
true on success, false if error is set |