[Dennis.van.d]

Thanks, latest build seems to resolve the issue.

[Dennis.van.d]

Hi

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.

[Dennis.van.d]

Thank you very much, this is indeed the future I was looking for.

[Dennis.van.d]

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.

 

[Dennis.van.d]

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.

 

 

 

[Author]

Posts