It might work, but I wouldn't count on it. With regards to your question: I would not expect to much impact on binary compatibility due to standard version, but it would hardly surprise me if the choice affects some pre-defined preprocessor symbols, in a way that would break binary compatibility in the library, much as if you'd compiled some of the modules with _GLIBCXX_DEBUG, and some without. On the other hand, be aware that preprocessor definitions of _GLIBCXX_DEBUG and _GLIBCXX_DEBUG_PEDANTIC will affect binary compatibility (although g++ ensures that you will get a library version which works with them if you use them consistently). Again, the safest bet is that all of the defines be identical, but also again, some common sense is in order: one can hardly expect the standard library to have been compiled with preprocessor symbols which are used in your project (things like MYPROG_CONFIG_FILE_LOCATION, say). in g++) won't affect binary compatibility, and that options which affect code generation (language level, etc.) might: g++ generally maintains compatibility across different levels of optimization, where as VC++ doesn't.Īnother real problem is defining preprocessor symbols in the command line. (Documentation which is sorely lacking in most compilers.) In practice, in the lack of documentation, it seems a safe bet that options which control warnings ( -W. The safest solution is to assume that all of the compiler options are identical, except when the compiler specifically documents that the option doesn't affect binary compatibility. Consequently, the following steps only need to be done once per library.Can different GCC dialects be linked together?Ī priori, no. We are going to do this on a global basis so the library will be available to all of our projects. Steps 3 and 4 - Tell the compiler where to find headers and library files See the tutorial on static and dynamic libraries for more information about this step. Steps 1 and 2 - Acquire and install libraryĭownload and install the library to your hard disk. Make sure the program know where to find any dynamic libraries being used.#include the library’s header file(s) in your program.Tell the linker which static or import library files to link.
Tell the linker where to look for the library file(s) for the library.Tell the compiler where to look for the header file(s) for the library.Unzip it to a directory or install it via a package manager. Download it from the website or via a package manager. To recap the process needed to use a library:
0 kommentar(er)
