Actually, I must confess that I hadn't set up the PATH correctly, so it
would just come up, and sit there.
Once I added the CW directory to the PATH, it came up and did its thing. But
I still don't like this all that much. Currently, we are doing our build
from a logged-in session, but would like to launch the build as an
unattended NT service, which won't be able to put up these screens.
Of course, VB also has similar problems, but at least it doesn't put up a
**** GUI while it's building..
-----Original Message-----
Date: 21 Dec 1999 23:25:35 -0800
From: "Scott Johnson (WA)" <[EMAIL PROTECTED]>
Subject: RE: Command-line invocation of CodeWarrior compiler?
> From: Shankar Unni [mailto:[EMAIL PROTECTED]]
> "cmdide.exe" [...] doesn't do what it advertises (it just pops up the GUI
> and sits there, regardless of what options I give it, or gives me an error
CMDIDE.EXE is what you are looking for. If you run it without any options,
it tells you to use the "/?" option to get a help screen. It works fine for
me. What options are you trying and what errors is it reporting?
