2023-05-31 11:14 AM
STM32CubeIDE v1.12.0
This type question has been asked different ways but never specifically for a procedure. In the past we have used Eclipse Workspaces with a single project and we were able to copy, paste and rename the Workspace and then open it as a different Worspace without issues. Attempting to do this in STM32CubeIDE results in a identical Workspace(except for the directory name) but with the Workspace location that can not be modified.
If you open the Project properties==>Resource, the Path of the project is relative to the Location(which is the Workspace location), but the Location(Workspace) is not. We have not found a way to modify this Location so the Workspace/Project now has a fixed Location in the original users path.
Thanks
2023-05-31 12:09 PM
After digging in the Properties=>Resource=>Linked Resources=>Path Variables, the "PROJECT_LOC" appears to be the original directory that had been copied. The PARENT_LOC, and WORKSPACE_LOC are the new directory. If you search through all the files in the new Workspace, there is only one that contains the text "PROJECT_LOC":
C:\Temp\Workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings\org.eclipse.core.resources.prefs
Modifying the PROJECT_LOC path in this file does not make a difference after reopening the Workspace.
2023-05-31 12:44 PM
Properties=>C/C++ General, click on Configure Workspace Settings, new window.
Preferences=>General=>Workspace=>Linked Resources.
This page shows a PROJECT_LOC. Modifying the org.eclipse.core.resources.prefs file causes changes here. Not sure why the PROJECT_LOC variable listed in the Project properties==>Resource=>Linked Resources=>Path Variables does not match.
2023-06-01 06:44 AM - edited 2023-11-20 04:17 AM
We just check a different company project the uses STM32CubeIDE v1.9.0 and the Workspace copy/paste method works correctly. PARENT_LOC, PROJECT_LOC and WORKSPACE_LOC all use the same Workspace directory(the PROJECT_LOC also tags on the Project directory.) Is this a STM32CubeIDE version issue or is it something about the way the original project was created? Can someone from ST tell us why the PROJECT_LOC is locked or maybe why that would happen?
Thanks.
2023-06-30 05:46 AM
Just to close this out we ended up taking this project and re-importing it into a new one. After the import was done, PARENT_LOC, PROJECT_LOC and WORKSPACE_LOC all use the new Workspace directory.