September 18, 2019 at 21:29 #25830
Hi I recently started using visualGDB, and started importing existing projects.
Currently we use BSP files per project/solution so that it will be build with the same BSP files. (even years later)
Is there a way to specify the shared files location per solution?
I know I can modify the makefile, but this will get overwritten if I change stuff through the visualGDB GUI.
So would be nice if you can define the shared files location relative to the project or set the $(BSP_ROOT) per solution.
DennisSeptember 19, 2019 at 03:03 #25832
Yes, VisualGDB allows relocating the BSP to an arbitrary location under your source control (see this tutorial).
Once the BSP is relocated, VisualGDB will remember its location on that machine and will automatically configure BSP_ROOT for all related projects to point to it.September 19, 2019 at 08:15 #25836
I don’t want the configure the BSP_ROOT root per machine, but per solution.
We have projects using the same micro but targeted against different BSP files (versions).
It seems I’m unable to make the BSP_ROOT relative to the project or to leave it Empty using visualGDB GUI.September 19, 2019 at 16:21 #25841
Thanks for the clarification. You can easily configure VisualGDB to maintain multiple simultaneous versions of the BSP via a checkbox under Tools->VisualGDB->Manage VisualGDB Packages->BSPs. After the multi-version mode is enabled, you can relocate each BSP version to a specific location in your source tree. Would that work for you?September 20, 2019 at 14:06 #25842
kinda, still have to add an absolute path and still not per solution.
We use git sub-modules so that the correct BSP files are copied into the project when it’s get cloned.
As stated before we use different BSP versions and even different branches of the same version due to modified vector tables and other tweaks.
That’s why I was wondering if I could have a relative path or leave the BSP blank.November 29, 2019 at 05:06 #26638
Just wanted to let you know that we have improved the BSP referencing logic in the following VisualGDB build: VisualGDB-184.108.40.20604.msi.
You can now use the VisualGDB Project Properties -> Embedded Project -> Shared Files -> Change button to switch between 2 modes of referencing a BSP:
- Using a global path shared between all projects
- Explicitly specifying the relative path to the BSP
Hope this helps. Let us know if you have any further suggestions/feedback.November 29, 2019 at 14:26 #26654
Thank you very much, this is indeed the future I was looking for.November 29, 2019 at 22:04 #26664
I have seem to run into an issue with this latest feature. If believe it’s related to solutions that contain stand-alone projects.
If I open a solution containing a stand-alone project, visualGDB shows me a window that it’s unable to locate the BSP files.
Trying to resolve this results in a system exception. (see screenshot)
Attachments:You must be logged in to view attached files.November 29, 2019 at 22:09 #26666
Sorry about that. We have just caught this with our pre-release tests as well. Please try this build: VisualGDB-220.127.116.1110.msiDecember 2, 2019 at 10:47 #26690
Thanks, latest build seems to resolve the issue.
You must be logged in to reply to this topic.