{"id":5857,"date":"2020-03-31T09:34:44","date_gmt":"2020-03-31T16:34:44","guid":{"rendered":"https:\/\/visualgdb.com\/w\/?p=5857"},"modified":"2020-10-27T12:21:50","modified_gmt":"2020-10-27T19:21:50","slug":"libraries-and-other-linker-inputs","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/documentation\/linkerinputs\/","title":{"rendered":"Libraries and Other Linker Inputs"},"content":{"rendered":"

VisualGDB uses the standard Linux way of specifying libraries used by the projects that relies on 3 different parameters:\"\"<\/a><\/p>\n

    \n
  1. Library directories.<\/strong> These are the directories where the GNU linker will search for libraries specified in “Library names”. Locations like \/usr\/lib will be searched by default and do not need to be specified.<\/li>\n
  2. Library names.<\/strong> This line contains short library names<\/strong> of libraries that should be linked with the project. The short library names do not contain the ‘lib<\/strong>‘ prefix or the .a<\/strong> extension. E.g. in order to link with libpthread.a<\/strong> and libm.a<\/strong> this line should contain “pthread m<\/strong>“. If you need to use a specific version of the library (e.g. libboost_system.so.1.61.0<\/strong>), you can specify it here prefixed with a colon (e.g. “:libboost_system.so.1.61.0<\/strong>“), or enter the full path to the library in the Additional Linker Inputs<\/strong> field.<\/li>\n
  3. Additional linker inputs.<\/strong> This line can specify full paths to additional library or object files that should be linked with the project. This can be used to link against a specific version of a library, e.g. \/usr\/lib\/i386-linux-gnu\/libpthread.so<\/strong>. If you are using a cross-toolchain, use the ‘=’ prefix to specify a path inside the sysroot directory (e.g. =\/usr\/lib\/arm-linux-gnueabihf\/libboost_system.so.1.61.0 <\/strong>will expand to c:\\SysGCC\\raspberry\\arm-linux-gnueabihf\\sysroot\\usr\\lib\\arm-linux-gnueabihf\\libboost_system.so.1.61.0<\/strong>)<\/li>\n<\/ol>\n

    It is recommended to specify libraries using the short names and directories, however if this causes problems (e.g. when using cross-compilation toolchains), it may be helpful to specify full paths to all necessary libraries using the “Additional Linker Inputs” line.<\/p>\n

    Diagnosing Linker Problems<\/h2>\n

    The 2 most common types of linker errors are:<\/p>\n