What is the recommended way to structure an M2MStudio project so that it can be built for different targets?
eg, GPIO handling changed significantly between OS 4.25 and 6.20 - see: viewtopic.php?f=46&t=3654&p=14112&hilit=changed+significantly#p14112
So, say, if one has some devices in the field with OS 4.25 and some with 6.20, how can an M2MStudio project best be structured to support both these targets?
With Visual Studio, I did it by having an OS_425 project in a folder with 4.25-specific files, and an OS_620 project in a folder with 6.20-specific files, and another folder with “common” files:
Product Folder--+---OS_425 Project--+--inc | | | +--src | +---OS_620 Project--+--inc | | | +--src | +---Common----------+--inc | +--src
I used the -src and -inc Project Wizard options to specify the location of the Common files.
M2MStudio doesn’t seem able to cope with this - it ends up duplicating loads of files!
It looks like the “Build Configurations” might be the way to go, but I’m not quite sure what they’re really about from the online help.
In particular, I need to ensure that the 4.25-specific files are not built for the 6.20-specific “target”, and vice-versa.