Dear,
i use the following scenario:
1. i have a project for static library
2. i have a project for linux application
3. i use project dependency and include the static lib into my linux app
4. i get link errors
The link errors are because visualgdb adds in my case staticlib.a to the end of linking and i get all sorts of unresolved sybols (libdl, libcrypto….
If i manualy move the custom static lib in front of all other shared or static libs then it works…
So my question is, is my problem isolated or does Visualgdb has a problem with project dependency as it should probably automaticly put the static lib first in order…
Best regards,
Lonko