Surely a build engine invokes the compiler, assembler, linker & loader in sequence? Therefore it does spawn/chain/execute the compiler. Sounds like CmdIDE extract the compiler command line from the MCP file based on the target modifier. Sounds reasonable, I just wish it were more flexible.
I know I can set up varying targets, each with specific compiler options, and then CmdIDE will accept target as a parameter. But what if I want to have a command line build that takes in a specific customization? Thing is, I have a code generator which I will be giving to a technician, and that feeds some source code into the build process. I want to give the build a path to the custom code to include.
I did try a "hack" of the MCP file, something I didn't want to do as there was binary and ascii mixed, and as expected it fried the MCP file and auto recovery messed up the MCP so I couldn't just undo the edit.
So I too am now looking at how to export the MCP into a make file or XML file. Something that is ASCII, and I can edit with a SED like script. I believe I saw CmdIDE accepts an XML file.
/x <project.xml> specifies an XML project file to import
(A project file argument must also be specified for the
name of the imported project. Once the project has been,
imported, build or debug operations may commence)
I do have two other options to explore - one is use of known fixed locations for custom files, the other is use of environment variables. I was just hoping that a simple cmd line interface to the compiler existed.