Hi there! In a few weeks, I might have to derive a product from another products. The hardware is the same, but the software is slightly different. I think, it would be a drag to copy the sources to another directory and and take care of two code versions. So it would be nice to know, which project it is while compilation time, so that I could use some #ifdef statement to get conditional compilation. Other than that, I just had the idea to have a "higher source level files that define a compiler constant and then include the low level source files. Like:
"highlevel.c" #define OEM #include "lowlevel.c" "lowlevel.c" #ifdef OEM #include ... #else #include ... #endif // some common source #ifdef OEM // OEM source only #else // non OEM source #endif // some common source
Here is my experience. (In other words why I gave up on targets and now make separate UV2 projects.) UV2 is "different" than other IDE's. In other IDE's you create "targets" each having there own "file source list" (and options). In the UV2 IDE's you create one "file source list" which contain "targets" that have there own "exclude from the build list" (and options). In other words all "targets" share the same file list. To remove a file you must leave it in the list and set "exclude from the build flag". To add a file you must add it and then go to all the other "targets" and set their "exclude from the build flag".
Ahhh. I think I understand. Are you creating complete different programs? If that's the case, then you should create a separate project for each program. If you are creating the same program (just for different chips or configurations) then uVision2 targets and groups works beautifully. To further explain... I have a project with about 25 targets. Each target generates a program for a different 8051 derivative. Each target creates the same program--just for a different chip. I have targets for Philips MX, Dallas 390, Infineon C167, Standard 8051, and so on. Most of the files in my project are common between all targets. However, I do have some special files (device drivers, mainly) that are only included for each target. So, I have a file group for Philips MX, Dallas 390, Infineon C167, and Standard 8051. The Philips MX group is set as "Do Not Include" for all targets bu the Philips MX. The same goes for the Dallas 390, Infineon C167, and Standard 8051. When I start a project that I know I will use on multiple targets, I create a group for each target (so I can put target-specific files there). Then, in my first target, I set these as "Do Not Include". When I create new targets, I copy the settings of the original target. Then, all I must do is enable the required groups for the new target. But, hey. That's just my solution. Jon