[hvbill]

Good to know about the floating license key in the registry.
But what about the BSP:s when there is more than one user on the computer? Aren’t they installed in C:\Users\UserName\AppData\Local\VisualGDB\EmbeddedBSPs\ and then personal?

[hvbill]

Update.

I have successfully updated a static license to a floating one. It was easy and it works great. Thanks for that.

But still the problem remains with the installation that is user specific and not available for all users of the computer, including the Local System account.

Next step will probably be to try to install VisualGDB as Local System account using Microsoft psexec tool.

[hvbill]

Thanks for the new OpenOCD build. Unfortunately it didn’t help, but your support is really great.

Looking into the OpenOCD output above once again, could it have something to do with GDB?

[hvbill]

Forgot to mention that I’ve read this post

Getting warning about overriding recipe and ignoring old recipe on library proje

But I can’t remove the linker script.

[hvbill]

The registry workaround will most likely work for us.

Is the behaviour different in VS2017?

[hvbill]

Found that this has been fixed in VisualGDB 5.4.

Great!

[hvbill]

I have the same issue when there is a comment on the line above. Both in live coding and when using ctrl k + f.

 // Comment
 if(test)
 {
   DoSomething();
 }

I’m running VisualGDB 5.3R8

• This reply was modified 5 years, 7 months ago by hvbill.
• This reply was modified 5 years, 7 months ago by hvbill.

[hvbill]

That workaround would be really nice to have.

Thanks!

 

 

 

[hvbill]

We are using VisualGDB 5.3R6 and Visual Studio 2015

[hvbill]

It works perfectly!

Tack så mycket!

[hvbill]

I don’t find the Additional Include Directories mentioned above, but there is a line called Include Search Path with similar content (see attached image), and it also use absolute paths.

But in VisualGDP Project Properties -> Makefile settings -> Include directories, I finally found my relative paths. These include paths are stored in debug.mak/gcc_Debug.h with relative paths but as soon as I change something in VisualGDP Project Properties, .vcxproj is updated with absolute paths.

I don’t see how we can avoid to share the .vcxproj file via source control so is there a way to have relative paths there as well?

 

Attachments:

You must be logged in to view attached files.

[hvbill]

We’re working in Windows, targeting an ARM-platform. And when I try to replace any of the paths to D:\ (see the attached image) with relative paths, they get replaced with absolute ones the next time a setting is changed that makes VisualGDB test the selected toolchain.

[Edit: uploaded new image]

• This reply was modified 6 years, 6 months ago by hvbill.

Attachments:

You must be logged in to view attached files.

[Author]

Posts