Dear all,
a couple of years ago I remember that I used a feature in UV3 and now this feature does not work anymore in the latest release of uVision.
I defined two targets in the same project: target1 and target2 for two different micros, and it was possible to use different files in the two targets (the asm startup files for instance).
I did that using the "Project Components" dialog window. On current release of UV4 this window is available on the menu Project/Manage/Components ... .
Now I am trying to do the same, but the changes I do to the dialog window fall in every Project Target, so all my targets have the same files.
Does it happen to you also? Is it a removed feature or I am doing something wrong?
I thank you all in advance, Marco.
One project may contain one boot loader, and may build applications for multiple variants of the same base product.
But different hardware have their own boot loaders, so there is no use to try to share the code for a boot loader for a M2M automitive comminucations device with a controller for LED displays.
No, I am not mixing the function of the project files with the use of version control software. But it is a question of mind-set when managing the source for a large number of different prodocuts. Some products possibly co-owned with another company.
History have already shown the result of having related parts splitted into separate projects. The repository may not always be local. One little quick corporate action may over a day separate the build machines from the repository. And people may quit or departments shut down. When big things happens, it helps if: - it is obvious for the people with a huge repository what is stored where. - it is obvious for the people with the build machines what directories that forms a product - it is obvious for the people with a CD burned 10 years earlier, what directories or zip files that forms a product
In the end, you want multiple, independent, ways to be able to figure out what you have, and how to combine it to a working firmware.
One company I worked for, sold parts of their operation. The buyer later decided to close one of the offices. The people who did take some backups of some of the machines then did not have an inkling what to back up - or even why to bother. Especially since the poeple with the knowledge was the people who got a new job before the office closed. Some machines got scrapped. Some got reformatted and sold or reused in other offices. The backup tapes from the bank box got thrown away since no one knew what to do with them.
Yes, you could say that I have a bit of experience when it comes to recreating software 10-15 years after a company merger etc did wreak havoc.
Projects should be self-contained, every step of the way.
You don't have to agree, but do take it into consideration. It might some time help.