Just at a quick thought here are a couple on either side.
Command line:
More control over the exact compilation process and linking as well.
Some say that it allows one to carry a compiler with you on media, though I don't
know why you'd want to do that.
It can be very confusing at times what switches are needed, and even harder to
document them.
Not every user on every machine in every network will have access priviliges to a
command prompt, so it may require that the account's sysadmin be contacted.
IDE:
Quick start on any project, most compilation switches can be readily seen and
modified, IF you are familiar with the IDE's tools and options.
Integrated debugging can save time compared to a command prompt where each
new compile must be invoked into a debugger, profiler, etc. separately.
IDEs can be difficult to learn all the controls and options available for a beginner.
IDEs tend to hide what options are active, so errors at build time may not be
easily identified as switches being miss set.
An IDE's automatic project update can become corrupted under certain conditions,
making it necessary to interdict the make utility by hand anyway.
