Hi all,
i have a problem selecting the active project to build. As visible in the image i have activate utasker serial bootloader but this part remain with a bar on the file and folder. Why?
Thanks
Solved! Go to Solution.
Hi Daniele
Whatever target you select the "strike thoughs" stay the same.
That is, if you select the uTaskerSerialBoot it will remain grayed out and the uTaskerV1.4 target remains without the strike-through (although the build target uTaskerSerialBoot is really active).
If you build the project you will find that the correct target is really built and the correct files are used.
Eg. The output file uTaskerSerialLoader_FLASH will be created if not already there, and the objects inside that folder are also updated correctly.
I have however found away to correct this behaviour:
1. Open the main project properties and then expand C/C++ General, followed by Indexer
2. Enabled "Enable project specific settings"
3. Change the radio button from "Used a fixed build configuration" to "Use active build configuration"
Now the strike throughs will correctly follow the seleted target.
It seems that the default behaviour is for CDT not to display the active target, and the active target is only controlling the build. With this adjusted setting it keeps the two together, which makes a lot more sense!
From what I have seen, CodeWarrior and Atollic display automatically follows the active target, based on the fact that I didn't experience this effect before, although it may have started at a certain point, even if never actually knew the setting exists untill recently!
Regards
Mark
Hi Daniele,
these 'bars' are 'icon decorators' in Eclipse. See Icon and Label Decorators in Eclipse | MCU on Eclipse for a list of common decorators. The 'strike through' bar means that the file has been excluded from that build configuration.
I hope this helps,
Erich
Hi Daniele
Whatever target you select the "strike thoughs" stay the same.
That is, if you select the uTaskerSerialBoot it will remain grayed out and the uTaskerV1.4 target remains without the strike-through (although the build target uTaskerSerialBoot is really active).
If you build the project you will find that the correct target is really built and the correct files are used.
Eg. The output file uTaskerSerialLoader_FLASH will be created if not already there, and the objects inside that folder are also updated correctly.
I have however found away to correct this behaviour:
1. Open the main project properties and then expand C/C++ General, followed by Indexer
2. Enabled "Enable project specific settings"
3. Change the radio button from "Used a fixed build configuration" to "Use active build configuration"
Now the strike throughs will correctly follow the seleted target.
It seems that the default behaviour is for CDT not to display the active target, and the active target is only controlling the build. With this adjusted setting it keeps the two together, which makes a lot more sense!
From what I have seen, CodeWarrior and Atollic display automatically follows the active target, based on the fact that I didn't experience this effect before, although it may have started at a certain point, even if never actually knew the setting exists untill recently!
Regards
Mark
Thanks!!!