Honestly, if I understand correctly what a cross-compiler is, I think it must be one of the stupidest ideas ever. Suddenly you require that everybody who gets your code uses your custom compiler to build it?
And for what benefit, not passing "problematic" parameters to the compiler?
Also if the user's compiler cannot build your code in the required object file format, that's not your fault, and it's not your code's fault either.
But I'm willing to learn, so if what I said above is misguided do correct me.
Well judging by the site LB listed it is probably an OS
Actually I'm only interested in the cross compiler, OS is still out of my league and out of my interest. I want to develop my own API for the Vex Cortex Microcontroller - the two 'official' ones (those provided by EasyC and RobotC) are not satisfactory to me.
@Catfish: normally you compile to target the system you are compiling on. Cross-compiling is targeting a different system/architecture than the one you are compiling on, e.g. targeting windows while compiling on linux, or vice-versa. In my case I am targeting arm-none-eabi while compiling on x86_64-w64-mingw32.