In general, this option is a little easier to maintain, as it's just setting up the linker, you don't mess up with source code in any way (and defining a preprocessor constant is messing up with the source code in potentially ugly ways).Īlso, with this option it's simple to turn a constant into a runtime parameter, which can be changed during the execution of the program, if need be - just drop the const from the declaration and definitions. In that case, you would have a single header like: extern int const constant_x Īnd then a separate source file for each platform: // platform_a.cĪgain, how to link in only the source file that you need for a particular target depends on your build system and I'm not familiar with Keil IDE, but it should not be hard to do. I don't have experience with Keil IDE's, so, I'm not sure how to configure it to build different binaries with different macro definitions, but, it's a common C thing, there should be way to do it.Īnother option would be to make these globals.
This option is the only way if you use these constants to, say, dimension an array. Of course, if you have a lot of constants, maybe keeping each platform in its own header would be better (easier to read). How to Compile C Program with KEIL MK Subramanian 7K subscribers Subscribe 81 Share Save 25K views 8 years ago How to Compile C, C++ Programs into HEX file for your own Projects.
I'll assume your constants are macros, but, it should not be different if they are enums or something else.įirst option is to use the preprocessor to select your platform. Let me show you two ways to solve your problem which I believe are much better. Understanding where you're coming from, I would not recommend going down the road you suggested.
0 kommentar(er)
