Sure, but invoking a compiler from a command line is something you can easily pick up from a coworker or an internet tutorial.
The primary focus of an intro engineering course is (usually) about the theory and structure of computing, along with general techniques for writing code.
Learning about various build tools distracts from that focus.
EDIT: Also, you seem to be implying (apologies if I'm wrong) that invoking a compiler from a command line is somehow "better" than using IDE. Why?
My intro course used BlueJ, which is (was?) some sort of dumbed down Java IDE specifically for students. The thought was that dealing with all of the crap surrounding software development, like make systems, editors, compiler flags, etc was a distraction from learning basic programming constructs. Looking back I agree completely. As a new programmer, things like compiler flags are pretty much black magic. You don't really learn anything by reciting magic spells.
Learning development tools like the CLI, IDEs, debuggers, linters, et. al. should be required for a CS degree. I don't think an intro course is the right setting.
The primary focus of an intro engineering course is (usually) about the theory and structure of computing, along with general techniques for writing code.
Learning about various build tools distracts from that focus.
EDIT: Also, you seem to be implying (apologies if I'm wrong) that invoking a compiler from a command line is somehow "better" than using IDE. Why?