child's current working directory, or NULL to inherit parent's. [allow-none]
child's argument vector. [array zero-terminated=1]
child's environment, or NULL to inherit parent's. [array zero-terminated=1][allow-none]
flags from GSpawnFlags
function to run in the child just before exec(). [scope async][allow-none]
user data for child_setup. closure
return location for child process reference, or NULL. out[allow-none]
TRUE on success, FALSE if error is set
GException on failure.
See g_spawn_async_with_pipes() for a full description; this function simply calls the g_spawn_async_with_pipes() without any pipes. You should call g_spawn_close_pid() on the returned child process reference when you don't need it any more. Note 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 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.