Is there a C-compiler (and for that matter C++ compiler) for windows that
can be run from the commmand line?
>
>
All of them can be run from the command line
o MSVC. In your installation tab there is a visual studio
tools item. Open it and choose the command line option. That
will open a command shell with all the necesary environment variables
alraedy set.
o mingw. Install it, add the binaries directory to your path, then
just use it with "gcc options"
o Pelles C: Just install it, go to the installation directory and
use the .bat that sets the environment variables
o lcc-win. Just add \lcc\bin to your path and compile with
lc <arguments>
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
Is there a C-compiler (and for that matter C++ compiler) for windows that
can be run from the commmand line?
Yes. Borland C (and its little brother Turbo C), Microsoft C, Pacific C,
gcc, Digital Mars C, Pelles C (and no doubt plenty more) can all be run
from the command line. Your current C compiler can almost certainly do it.
Check the documentation.
--
Richard Heathfield <http://www.cpax.org.uk >
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
Is there a C-compiler (and for that matter C++ compiler) for windows
that can be run from the commmand line?
As far as I know all compilers that come with IDEs can also be run from
the command line. This includes MSVC, Intel, gcc, Borland, lcc-win,
PellesC etc. Your compiler's documentation will tell you what the
actual command is to invoke the command line compiler and bypass all
the IDE stuff.
But just to get you up and running here are the names of executables
that you need to invoke for compiling from the command line.
MSVC - cl.exe
gcc - gcc (gcc.exe on Windows)
Borland - bcc.exe (and tcc.exe for their "Turbo C" branded products)
lcc-win32 - lcc.exe
Intel - icc (or icc.exe)
But there is no substitute for reading the documentation that comes with
your compiler and Standard library.
>Is there a C-compiler (and for that matter C++ compiler) for windows that
>can be run from the commmand line?
>
Yes. Borland C (and its little brother Turbo C), Microsoft C, Pacific C,
gcc, Digital Mars C, Pelles C (and no doubt plenty more) can all be run
from the command line. Your current C compiler can almost certainly do it.
Check the documentation.
You forgot to mention lcc-win. Available free for home use.
>>Is there a C-compiler (and for that matter C++ compiler) for windows that
>>can be run from the commmand line?
>Yes. Borland C (and its little brother Turbo C), Microsoft C, Pacific C,
>gcc, Digital Mars C, Pelles C (and no doubt plenty more) can all be run
>from the command line. Your current C compiler can almost certainly do it.
>Check the documentation.
>
You forgot to mention lcc-win. Available free for home use.
>
Yeah, bad memory this heathfield...
Thanks for remind him of lcc-win
:-)
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
>>rufus said:
>>>
>>>Is there a C-compiler (and for that matter C++ compiler) for
>>>windows that can be run from the commmand line?
>>Yes. Borland C (and its little brother Turbo C), Microsoft C,
>>Pacific C, gcc, Digital Mars C, Pelles C (and no doubt plenty more)
>>can all be run from the command line. Your current C compiler can
>>almost certainly do it. Check the documentation.
>>
>You forgot to mention lcc-win. Available free for home use.
>>
>
Yeah, bad memory this heathfield...
As long as lcc-win doesn't fully conform to either the C89- or C99-Standard,
he doesn't regard it a C-compiler, or did that slip your memory? ;-)
>>rufus said:
>>>
>>>Is there a C-compiler (and for that matter C++ compiler) for windows
>>>that can be run from the commmand line?
>>Yes. Borland C (and its little brother Turbo C), Microsoft C, Pacific
>>C, gcc, Digital Mars C, Pelles C (and no doubt plenty more) can all be
>>run from the command line. Your current C compiler can almost certainly
>>do it. Check the documentation.
>>
>You forgot to mention lcc-win. Available free for home use.
>>
>
Yeah, bad memory this heathfield...
The troll is mistaken (as usual), and so are you (as usual). I didn't
"forget" to mention lcc-win. The OP asked for command-line-driven C
compilers. As far as I'm aware, lcc-win doesn't claim conformance to
either C90 or C99, so how can it be called a C compiler?
--
Richard Heathfield <http://www.cpax.org.uk >
Email: -http://www. +rjh@
Google users: <http://www.cpax.org.uk/prg/writings/googly.php>
"Usenet is a strange place" - dmr 29 July 1999
>>Richard Heathfield <rjh@see.sig.in validwrites:
>>>
>>>rufus said:
>>>>
>>>>Is there a C-compiler (and for that matter C++ compiler) for
>>>>windows that can be run from the commmand line?
>>>Yes. Borland C (and its little brother Turbo C), Microsoft C,
>>>Pacific C, gcc, Digital Mars C, Pelles C (and no doubt plenty more)
>>>can all be run from the command line. Your current C compiler can
>>>almost certainly do it. Check the documentation.
>>You forgot to mention lcc-win. Available free for home use.
>>>
>Yeah, bad memory this heathfield...
>
As long as lcc-win doesn't fully conform to either the C89- or C99-Standard,
he doesn't regard it a C-compiler, or did that slip your memory? ;-)
>
Bravo!
I think you have earned some points here. Soon you will be a
member of the regulars clique!
Just keep the good work
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
>>Richard Heathfield <rjh@see.sig.in validwrites:
>>>
>>>rufus said:
>>>>
>>>>Is there a C-compiler (and for that matter C++ compiler) for windows
>>>>that can be run from the commmand line?
>>>Yes. Borland C (and its little brother Turbo C), Microsoft C, Pacific
>>>C, gcc, Digital Mars C, Pelles C (and no doubt plenty more) can all be
>>>run from the command line. Your current C compiler can almost certainly
>>>do it. Check the documentation.
>>You forgot to mention lcc-win. Available free for home use.
>>>
>Yeah, bad memory this heathfield...
>
The troll is mistaken (as usual), and so are you (as usual). I didn't
"forget" to mention lcc-win. The OP asked for command-line-driven C
compilers. As far as I'm aware, lcc-win doesn't claim conformance to
either C90 or C99, so how can it be called a C compiler?
>
You are lying, as always.
--
jacob navia
jacob at jacob point remcomp point fr
logiciels/informatique
>>Richard wrote:
>>>Richard Heathfield <rjh@see.sig.in validwrites:
>>>>
>>>>rufus said:
>>>>>
>>>>>Is there a C-compiler (and for that matter C++ compiler) for
>>>>>windows that can be run from the commmand line?
>>>>Yes. Borland C (and its little brother Turbo C), Microsoft C,
>>>>Pacific C, gcc, Digital Mars C, Pelles C (and no doubt plenty more)
>>>>can all be run from the command line. Your current C compiler can
>>>>almost certainly do it. Check the documentation.
>>>You forgot to mention lcc-win. Available free for home use.
>>>>
>>Yeah, bad memory this heathfield...
>>
>As long as lcc-win doesn't fully conform to either the C89- or
>C99-Standard, he doesn't regard it a C-compiler, or did that slip
>your memory? ;-)
>>
>
Bravo!
>
I think you have earned some points here. Soon you will be a
member of the regulars clique!
>
Just keep the good work
Between JoJo and Vippstar it must be hard for Heathfield to choose
his number one lackey!
>>Richard wrote:
>>>Richard Heathfield <rjh@see.sig.in validwrites:
>>>>
>>>>rufus said:
>>>>>
>>>>>Is there a C-compiler (and for that matter C++ compiler) for
>>>>>windows that can be run from the commmand line?
>>>>Yes. Borland C (and its little brother Turbo C), Microsoft C,
>>>>Pacific C, gcc, Digital Mars C, Pelles C (and no doubt plenty
>>>>more) can all be run from the command line. Your current C
>>>>compiler can almost certainly do it. Check the documentation.
>>>You forgot to mention lcc-win. Available free for home use.
>>>>
>>Yeah, bad memory this heathfield...
>>
>The troll is mistaken (as usual), and so are you (as usual). I didn't
>"forget" to mention lcc-win. The OP asked for command-line-driven C
>compilers. As far as I'm aware, lcc-win doesn't claim conformance to
>either C90 or C99, so how can it be called a C compiler?
>>
>
You are lying, as always.
So win-lcc _is_ claiming conformance to C90 or C99? Which one then? Or even
both? Which which switches?
I only remember severel reports here about non-conformance to either
standard, so if you claim win-lcc to be conforming _you_ seem to be lying
here...
>So win-lcc _is_ claiming conformance to C90 or C99? Which one then?
>Or even both? Which which switches?
C89 is supported
Which switches turn on full C89 conformance?
C99 is supported but there are a few things missing.
Which switch to turn this on? However, as long as things are missing, it is
not fully C99 conformant. Claiming otherwise would be a lie.
There is no half-way-conformant or nearly-there, that's like "almost
pregnant".
>I only remember severel reports here about non-conformance to either
>standard, so if you claim win-lcc to be conforming _you_ seem to be
>lying here...
>
What are the problems? Can you specify?
I remember several issues having been mentioned here in CLC, most recently
frand() from one of your standard headers.
I'm too lazy to dig up the other issues now, there were several in the past
few months and you perfectly know about them as you went balistic every
signle time one came up.
Hmm, maybe you can rightfully claim it to be C89 conformant, modulo bugs?
Comment