That I think that will cause a few problems if someone should write a module that requires certain compiler options and libraries to work. Having these options on a global scale would mean unnecessary search and linkages when not needed. As well as causing a headache for the writers of such modules and inexperienced users not knowing the changes in the environment file would mean that their simple Hello World application would require that their end users would need those unnecessary runtime libraries.
Edit:
I would suggest that the mx2cc checks for a environment file in the root folder of a project or module so the defaults can be overridden if needed.
|
