how to execute exe files from within a file

[Casanova]

Hello!

How can I execute other exe files from within a executable file in GCC.
In TurboC 3, the spawn command executes a file and returns command to
the calling file.

whereas in GCC, the exec command only starts the execution of the new
file and does not return command to the calling file (the calling file
is terminated on the start of execution of the called file)

Is there any command in GCC that after executing the called file,
returns command to the calling file. The called file should be able to
be run in both concurrently as well as putting the calling file on
hold.

Thank You

Casanova

[Lawrence Kirby]

On Thu, 16 Dec 2004 08:17:23 -0800, Casanova wrote:

Hello!

How can I execute other exe files from within a executable file in GCC.
In TurboC 3, the spawn command executes a file and returns command to
the calling file.

The standard C function to run external commands is called system() and is
declared in <stdlib.h>. If that won't do what you want (it probably will)
then a good newsgroup to discuss gcc is gnu.gcc.help, but note that gcc is
just a compiler, your question is really about what libraries you happen
to be using with it.

Lawrence

[Nick Keighley]

system()
--
Nick Keighley

[Chris Torek]

In article <11**********************@z14g2000cwz.googlegroups .com>
Casanova <pr********@gmail.com> wrote:

How can I execute other exe files from within a executable file in GCC.

See the comp.lang.c FAQ, question 19.27.
--
In-Real-Life: Chris Torek, Wind River Systems
Salt Lake City, UT, USA (40°39.22'N, 111°50.29'W) [phone]
email: forget about it http://web.torek.net/torek/index.html
Reading email is like searching for food in the garbage, thanks to spammers.

[Chris Croughton]

On 16 Dec 2004 08:17:23 -0800, Casanova
<pr********@gmail.com> wrote:

How can I execute other exe files from within a executable file in GCC.
In TurboC 3, the spawn command executes a file and returns command to
the calling file.
The only method specified in standard C is system().
whereas in GCC, the exec command only starts the execution of the new
file and does not return command to the calling file (the calling file
is terminated on the start of execution of the called file)

Is there any command in GCC that after executing the called file,
returns command to the calling file. The called file should be able to
be run in both concurrently as well as putting the calling file on
hold.

No (it would be in the system library rather than in GCC itself, so
check about your system libraries). The conventional way to do it on
Unix is to fork(2) a process which then calls exec(3) to run the
program, while the original process wait(2)s for it to complete. Or you
can use popen(3) which allows you to write to the program's standard
input or read its standard output. But these are outside the standard C
specification (although they are in the POSIX specification so are
standard on systems which are conformant to that, like most Unix
systems).

[Note: numbers in parentheses like fork(2) refer to the man(1) section
numbers...]

Chris C

[Casanova]

in system() i wont be able to pass parameters. I have to open a exe
file which has to take command line parameters.

And just in case this is relevant. I am programming for the windows
platform

[Jens.Toerring]

Casanova <pr********@gmail.com> wrote:

in system() i wont be able to pass parameters. I have to open a exe
file which has to take command line parameters.
Well, you pass the whole command line, including the parameters, to
system().
And just in case this is relevant. I am programming for the windows
platform

If this is relevant then you're off-topic here and you should better
ask in a MS programming group.
Regards, Jens
--
\ Jens Thoms Toerring ___ Je***********@physik.fu-berlin.de
\__________________________ http://www.toerring.de

[CBFalconer]

Casanova wrote:

in system() i wont be able to pass parameters. I have to open a exe
file which has to take command line parameters.

And just in case this is relevant. I am programming for the windows
platform

Of course you can pass parameters - you can pass anything you like
in a text string. What is done with them is not dependant on the C
language, but on the shell which which you are actually
communicating. That is system dependant, and OT here.

--
Chuck F (cb********@yahoo.com) (cb********@worldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net> USE worldnet address!

[Kenny McCormack]

In article <sl******************@ccserver.keris.net>,
Chris Croughton <ch***@keristor.net> wrote:
....

The conventional way to do it on Unix is to fork(2) a process which then
calls exec(3) to run the program, while the original process wait(2)s for
it to complete. Or you can use popen(3) which allows you to write to the
program's standard input or read its standard output. But these are
outside the standard C specification (although they are in the POSIX
specification so are standard on systems which are conformant to that,
like most Unix systems).
All of which is clearly irrelevant to (and most likely to utterly confuse)
the OP, since s/he is clearly a Windoze dork.
[Note: numbers in parentheses like fork(2) refer to the man(1) section
numbers...]

This, too.

[Chris Croughton]

On Fri, 17 Dec 2004 17:34:15 GMT, Kenny McCormack
<ga*****@yin.interaccess.com> wrote:

In article <sl******************@ccserver.keris.net>,
Chris Croughton <ch***@keristor.net> wrote:
...

The conventional way to do it on Unix is to fork(2) a process which then
calls exec(3) to run the program, while the original process wait(2)s for
it to complete. Or you can use popen(3) which allows you to write to the
program's standard input or read its standard output. But these are
outside the standard C specification (although they are in the POSIX
specification so are standard on systems which are conformant to that,
like most Unix systems).

All of which is clearly irrelevant to (and most likely to utterly confuse)
the OP, since s/he is clearly a Windoze dork.

If they are using GCC, as stated in the OP's question, they are likely
to have the rest of the libraries as well and be running with a
"Unix-like" environment such as Cygwin (under Windows) or DJGPP (under
MSDOS, likely since "Turbo C" was mentioned).

[Note: numbers in parentheses like fork(2) refer to the man(1) section
numbers...]

This, too.

Again, both Cygwin and DJGPP provide man.

Chris C