|
I have a project that runs from RAM, but can also be burned into flash. I'm trying to streamline the configuration using the project configurations feature. It won't let me use different linker .cmd files, so is ther way to add conditions to the linker .cmd file (I've tried #ifdef and .if and it won't accept them). Is it even possible to do this? Brian ----------------- Brian C. Lane (W7BCL) Programmer www.shinemicro.com RF, DSP & Microcontroller Design |
|
|
Conditional linker .cmd files?
Started by ●May 1, 2003
Reply by ●May 1, 20032003-05-01
|
Brian- > I have a project that runs from RAM, but can also be burned into > flash. I'm trying to streamline the configuration using the project > configurations feature. It won't let me use different linker .cmd > files, so is ther way to add conditions to the linker .cmd file (I've > tried #ifdef and .if and it won't accept them). > > Is it even possible to do this? <WARNING: KLUDGE AHEAD> Add a pre-processor step for each configuration, and copy over your a generic .cmd file with the correct file. The build then proceeds using the correct .cmd file. </KLUDGE> Yeah I know, not exactly the cleanest, but at least its automated. Until there is .NET for DSPs... -Jeff |
Reply by ●May 1, 20032003-05-01
|
Brian- > Well, they should have made the .cmd file part of the target settings > so you can easily change memory maps. Its just software, so it > shouldn't be too hard to do, right? <G> Allowing conditional statements in the linker .cmd file, and in the Visual Linker, would be better. Then the concept of different Active Configurations within a project would apply uniformly to all steps of the build process. Jeff Brower system engineer Signalogic |
