I am using microvision on Windows and I am surprised that the packs install to User\Appdata\Local\....
Is there a way to tell the pack installer to install to a different directory? I would think that I would like to install to a more "global" directory so that the entire software tree is visible to multiple users on my team - and not have each person install fundamental files to a unique location on each of their machines. The situation is made worse in that the vendor has placed the RTE_Device.h (and other files) in this location and has instructed me to edit them for certain configurations. I feel like I am missing something fundamental about the pack as I can't see User\Appdata\Local\.... as a useful place to store code that will be edited as part of a development/production process.
So ... is there a way to change the pack installation directory? And ... how do others handle pack installation and distribution for a team development environement?
Thanks for the info on the TOOLS.INI file. That is very helpful.
As to editing RTE_Device.h - could you please expand on why I don't need to edit it? And by edit - I mean use the configuration wizard - because it has to be writable for me to use the configuration wizard - and as far as I can tell, that is certainly required - at least on a board by board basis.
What you should not do is edit the RTE_Device.h file in the PACK directory. Create a new project and place it where you want to (not in the PACK directory). Feel free to run the configuration wizard and change the RTE_Device.h for your project. The reason they install these are read-only is so that people don't accidentally change the files in the PACK directory.
I am assuming that you have not actually tried to create your own project but are maybe looking at example projects that are in the PACK directory.
If you are using an example project from the PACK, don't try and edit it in the PACK area. You can copy a whole set of examples to some place that is yours and you can feel free to edit them there. If they are still read-only after copying them you can modify them so they are read-write.. You may use the configuration wizard on these files.
Thanks again - to be clear, I have made new projects as well as copied example projects. I agree that one shouldn't edit the files in the pack. I guess that is why I am so confused about how the pack is distributed and how the pack install directory isn't easily changeable. If I want to have my entire team to share the same codebase - then this pack needs to be placed in an area that isn't isolated on a single machine (neither the Appdata/Local nor the tool install directory C:\Keil_v5). I guess I will change the directory using the TOOLS.INI and have everyone on the team do the same.
I am curious how others are handling this is they want to have production code where they can revision control and archive the entire build. Again - I figured this would be such a standard thing to do - and I was looking for the "proper" way to do it. Somehow, editing TOOLS.INI seems like a bit of a hack.
This solution is also useful is your Windows username changes. You have to go into TOOLS.INI and update the username in the path.