Yahoo Web Search

Search results

1. Top results related to what is a static library?

   • What is the difference between a static library and a dynamic one

     Top Answer

     Answered May 04, 2018 · 50 votes

     This concept might be a little bit too broad to explain, but i will try to give you a basic idea from which you can study further.

     Firstly, you need to know what a library is. Basically, a library is a collection of functions. You may have noticed that we are using functions which are not defined in our code, or in that particular file. To have access to them, we include a header file, that contains declarations of those functions. After compile, there is a process called linking, that links those function declarations with their definitions, which are in another file. The result of this is the actual executable file.

     Now, the linking as I described it is a static linking. This means that every executable file contains in it every library (collection of functions) that it needs. This is a waste of space, as there are many programs that may need the same functions. In this case, in memory there would be more copies of the same function. Dynamic linking prevents this, by linking at the run-time, not at the compile time. This means that all the functions are in a special memory space and every program can access them, without having multiple copies of them. This reduces the amount of memory required.

     As I mentioned at the beginning of my answer, this is a very simplified summary to give you a basic understanding. I strongly suggest you study more on this topic.

     Check all answers on Stack Overflow

     1/5

   • What does 'target_link_libraries' do when the target is a static library and the target link is a static library too?

     Top Answer

     Answered Jul 12, 2021 · 7 votes

     In short

     When target_link_libraries is applied to the static library, it won't affect on the resulted library file. But it affects on the target in the similar way, as it would affect on the target of the shared library.

     So, you can use target_link_libraries both for static and shared libraries in the same manner.

     In details

     When applied to the static library, target_link_libraries doesn't have immediate effect on the creation of this library. That is, when static library will be created (as file), it won't store that linkage:

     add_library(MyStaticLib STATIC ${SOURCES} )target_link_libraries(MyStaticLib PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")# When file 'MyStaticLib.lib' will be created,# it will NOT be linked with 'opencv_world410.lib'.-

     (As you probably know, a static library doesn't store any information about the linkage, a static library is just a collection of object files.)

     But while the file with the static library doesn't store linkage information, the CMake target, which represents that static library, will be "aware of linkage". This can be useful in many cases:

     add_executable(myExe ...)target_link_libraries(myExe PRIVATE MyStaticLib)# When file 'myExe.exe' will be created, it WILL be linked with 'opencv_world410.lib'-

     add_library(MyStaticLibAnother STATIC ..)target_link_libraries(MyStaticLibAnother PUBLIC MyStaticLib)# "As if" following line is executed# target_link_libraries(MyStaticLibAnother PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")-

     # [In main project]install(TARGETS MyStaticLib EXPORT MyProject)install(EXPORT MyProject NAMESPACE MyProject::)-

     # [In another project]find_package(MyProject REQUIRED)# It creates the target MyProject::MyStaticLib which is# "aware of linkage" with 'opencv_world410.lib'.-

     • If in the same project you create an executable or a shared library, and link it with the static library (using target_link_libraries ), that executable will actually linked with the dependent library: add_executable(myExe ...)target_link_libraries(myExe PRIVATE MyStaticLib)# When file 'myExe.exe' will be created, it WILL be linked with 'opencv_world410.lib'
     • If in the same project you create another static library, and link it with the static one, the another static library will be "aware of linkage" both with the initial static library and its dependency. add_library(MyStaticLibAnother STATIC ..)target_link_libraries(MyStaticLibAnother PUBLIC MyStaticLib)# "As if" following line is executed# target_link_libraries(MyStaticLibAnother PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")
     • If you install your library target and export it using command install(TARGETS ... EXPORT ...) , then the library can be found with find_package . And that find_package will create a static library target, which will be aware of linkage with all its dependencies: # [In main project]install(TARGETS MyStaticLib EXPORT MyProject)install(EXPORT MyProject NAMESPACE MyProject::) # [In another project]find_package(MyProject REQUIRED)# It creates the target MyProject::MyStaticLib which is# "aware of linkage" with 'opencv_world410.lib'.

     Additionally, if you link a static library with a target (not with a plain file), and that target contains compile definitions or other information, applicable to the compile stage, the static library will be compiled using that compile information.

     Check all answers on Stack Overflow

     2/5

   • What does 'target_link_libraries' do when the target is a static library and the target link is a static library too?

     Top Answer

     Answered Jul 12, 2021 · 7 votes

     In short

     When target_link_libraries is applied to the static library, it won't affect on the resulted library file. But it affects on the target in the similar way, as it would affect on the target of the shared library.

     So, you can use target_link_libraries both for static and shared libraries in the same manner.

     In details

     When applied to the static library, target_link_libraries doesn't have immediate effect on the creation of this library. That is, when static library will be created (as file), it won't store that linkage:

     add_library(MyStaticLib STATIC ${SOURCES} )target_link_libraries(MyStaticLib PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")# When file 'MyStaticLib.lib' will be created,# it will NOT be linked with 'opencv_world410.lib'.-

     (As you probably know, a static library doesn't store any information about the linkage, a static library is just a collection of object files.)

     But while the file with the static library doesn't store linkage information, the CMake target, which represents that static library, will be "aware of linkage". This can be useful in many cases:

     add_executable(myExe ...)target_link_libraries(myExe PRIVATE MyStaticLib)# When file 'myExe.exe' will be created, it WILL be linked with 'opencv_world410.lib'-

     add_library(MyStaticLibAnother STATIC ..)target_link_libraries(MyStaticLibAnother PUBLIC MyStaticLib)# "As if" following line is executed# target_link_libraries(MyStaticLibAnother PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")-

     # [In main project]install(TARGETS MyStaticLib EXPORT MyProject)install(EXPORT MyProject NAMESPACE MyProject::)-

     # [In another project]find_package(MyProject REQUIRED)# It creates the target MyProject::MyStaticLib which is# "aware of linkage" with 'opencv_world410.lib'.-

     • If in the same project you create an executable or a shared library, and link it with the static library (using target_link_libraries ), that executable will actually linked with the dependent library: add_executable(myExe ...)target_link_libraries(myExe PRIVATE MyStaticLib)# When file 'myExe.exe' will be created, it WILL be linked with 'opencv_world410.lib'
     • If in the same project you create another static library, and link it with the static one, the another static library will be "aware of linkage" both with the initial static library and its dependency. add_library(MyStaticLibAnother STATIC ..)target_link_libraries(MyStaticLibAnother PUBLIC MyStaticLib)# "As if" following line is executed# target_link_libraries(MyStaticLibAnother PUBLIC "${OPENCV_LIBS}/opencv_world410.lib")
     • If you install your library target and export it using command install(TARGETS ... EXPORT ...) , then the library can be found with find_package . And that find_package will create a static library target, which will be aware of linkage with all its dependencies: # [In main project]install(TARGETS MyStaticLib EXPORT MyProject)install(EXPORT MyProject NAMESPACE MyProject::) # [In another project]find_package(MyProject REQUIRED)# It creates the target MyProject::MyStaticLib which is# "aware of linkage" with 'opencv_world410.lib'.

     Additionally, if you link a static library with a target (not with a plain file), and that target contains compile definitions or other information, applicable to the compile stage, the static library will be compiled using that compile information.

     Check all answers on Stack Overflow

     3/5

   • What is the effect of changing the "Dynamic RTL" setting for a static library?

     Top Answer

     Answered Sep 27, 2012 · 7 votes

     I don´t use Embarcadero, but an older version of C++ Builder. I think they work the same way. When you use Dynamic RTL your code will call RTL functions from the runtime DLL´s that should shipped with your program. When you don´t use dynamic RTL, the functions are copied from libs into your exe or lib files. I use the dynamic RTL reduce the size of EXE files. The logic is the same for exe or libs. That means that if you use dynamic RTL in any module, be an exe or a lib, you will have to ship also the appropriate runtime DLL´s.

     Check all answers on Stack Overflow

     4/5

   • What is a static ArrayList?

     Top Answer

     Answered Nov 29, 2016 · 3 votes

     The keyword static before a variable in Java means that it is shared by all instances of that particular Class.

     Check all answers on Stack Overflow

     5/5

   Show moreShow less

2. en.wikipedia.org › wiki › Static_libraryStatic library - Wikipedia

   en.wikipedia.org › wiki › Static_library

   • Cached

   In computer science, a static library or statically linked library is a set of routines, external functions and variables which are resolved in a caller at compile-time and copied into a target application by a compiler, linker, or binder, producing an object file and a stand-alone executable.

3. www.geeksforgeeks.org › static-vs-dynamic-librariesStatic and Dynamic Libraries | Set 1 - GeeksforGeeks

   www.geeksforgeeks.org › static-vs-dynamic-libraries

   • Cached

   Aug 7, 2023 · Static Linking creates larger binary files, and need more space on disk and main memory. Examples of static libraries (libraries which are statically linked) are, .a. files in Linux and .lib . files in Windows. Steps to create a static library. Let us create and use a Static Library in UNIX or UNIX like OS. 1.

4. stackoverflow.com › questions › 140061When to use dynamic vs. static libraries - Stack Overflow

   stackoverflow.com › questions › 140061

   • Cached

   Sep 26, 2008 · A static library must be linked into the final executable; it becomes part of the executable and follows it wherever it goes. A dynamic library is loaded every time the executable is executed and remains separate from the executable as a DLL file.

   Code sample

   $$:~/dynamic [44]> cat foo.c

   #include<stdio.h>

   void foo() {

   printf("\nhello world\n");

   }...

   See more on stackoverflow

5. www.learncpp.com › cpp-tutorial › a1A.1 — Static and dynamic libraries – Learn C++ - LearnCpp.com

   www.learncpp.com › cpp-tutorial › a1

   • Cached

   A static library (also known as an archive) consists of routines that are compiled and linked directly into your program. When you compile a program that uses a static library, all the functionality of the static library that your program uses becomes part of your executable.

6. dev.to › iamkhalil42 › all-you-need-to-know-about-cAll you need to know about C Static libraries - DEV Community

   dev.to › iamkhalil42 › all-you-need-to-know-about-c

   • Cached

   Sep 4, 2020 · A static library is a file containing a collection of object files (*.o) that are linked into the program during the linking phase of compilation and are not relevant during runtime. As shown in the diagram above, when a program is compiled, the compiler generates an object file from a source file.

   • 
   • 
   • 
   • 

7. medium.com › @yakupcengiz › understanding-cUnderstanding C++ Libraries and Linking : Static vs. Dynamic

   medium.com › @yakupcengiz › understanding-c

   • Cached

   Sep 5, 2023 · Static library. A static library is a file that contains compiled code that can be linked directly into your application during compilation. When a program uses a...

8. People also ask

   What is a static library?

   • In computer science, a static library or statically linked library is a set of routines, external functions and variables which are resolved in a caller at compile-time and copied into a target application by a compiler, linker, or binder, producing an object file and a stand-alone executable.

   Static library - Wikipedia

   en.wikipedia.org/wiki/Static_library

   See all results for this question

   What are the advantages of static libraries?

   • One advantage of static libraries is that you only have to distribute the executable in order for users to run your program. Because the library becomes part of your program, this ensures that the right version of the library is always used with your program.

   A.1 — Static and dynamic libraries – Learn C++ - LearnCpp.com

   www.learncpp.com/cpp-tutorial/a1-static-and-dynamic-libraries/

   See all results for this question

   Can a static library be used as a dynamic library?

   • The static library is linked into the program at compile time, and then the functionality of the dynamic library can effectively be used as if it were a static library. On Linux, the shared object (.so) file works as both a dynamic library and an import library.

   A.1 — Static and dynamic libraries – Learn C++ - LearnCpp.com

   www.learncpp.com/cpp-tutorial/a1-static-and-dynamic-libraries/

   See all results for this question

   How to create a static library in C?

   • 1. Create a C file that contains functions in your library. We have created only one file for simplicity. We can also create multiple files in a library. 2. Create a header file for the library 3. Compile library files. gcc -c lib_mylib.c -o lib_mylib.o 4. Create static library.

   Static and Dynamic Libraries | Set 1 - GeeksforGeeks

   www.geeksforgeeks.org/static-vs-dynamic-libraries/

   See all results for this question

9. learn.microsoft.com › en-us › cppWalkthrough: Create and use a static library (C++ ...

   learn.microsoft.com › en-us › cpp

   • Cached

   Oct 28, 2021 · This step-by-step walkthrough shows how to create a static library (.lib file) for use with C++ apps. Using a static library is a great way to reuse code. Rather than reimplementing the same routines in every app that requires the functionality, you write them one time in a static library and then reference it from the apps.