I have a set of core modules common to my Crossworks 2.0 setup for ARM. I have different customers that use the core in different ways, all partioned off into a user.c file. I've been using #ifdef statements to select the correct path for the user.c file, but the nDef list is getting big. What would be nice is if there was a way of selecting / setting up a project in the Crossworks GUI that, via a drop down list, I can select the correct project that has that define set already.
Does anyone have any suggestions for making it easier and clearer what user.c file I am incorporating into my overall project?
Sorry if this seems vague ... just looking for an efficient way of including / excluding certain files from a project easily I guess...
Please sign in to leave a comment.