[scerion]

Thanks yes I did use that page to map the working GCC input to VisualGDB. I just realised the issue is with the libraries not being C++ compatible. After adding the extern “C” {} around the library headers they compiled. (I was using GCC to test, but VisualGDB is using G++)  Thanks!

• This reply was modified 3 years ago by scerion.

[scerion]

Thanks. It seems a bit hit and miss. Sometimes libraries need to be added to the “Library Names: ” field, sometimes not. Some libraries are not used even if added to this field,, or even added as a full path to the “Additional Linker Inputs:” field. For example, the “librpicopy” library simply cannot be used it seems. It finds the file ok, and intellisense doesn’t show errors, but upon building, the linker throws up errors about undefined references etc. I’ve checked the libraries have synced ok etc. I think to me, VisualGDB seems ok when compiling against some of the standard libs, but for some reason has problems with others, and it’s not clear why. Compiling the exact same code on the Pi itself works fine.

I did buy a license, but going ahead I think it’s probably more reliable to just build on the Pi curently. Thanks!

• This reply was modified 3 years ago by scerion.

[Author]

Posts