shared-libraries

I am trying to understand the fundamental of shared memory concept. I trying to create a shared library having one function and one STATIC array variable. I want to access static array variable through the function of that shared library. Here is my shared library //foo.c #include <stdio.h> static int DATA[1024]={1 ,2 ,3 ,...., 1024}; inline void foo(void) { int j, k=0; for(j=0;j<1024;j++) { k=DATA[j]; } k+=0; } I have created shared library object (libfoo.so) by following instructions from shared library Now my questions are 1> If I access foo() from two different program ( program1 and

We are in the process of designing a new C++ library and decided to go with a template-based approach along with some specific partial template specialisations for corner cases. In particular, this will be a header-only template library . Now, there is some concern that this will lead to a lot of code duplication in the binaries, since this template 'library' will be compiled into any other shared library or executable that uses it (arguably only those parts that are used). I still think that this is not a problem (in particular, the compiler might even inline things which it could not across

I have a bunch of static libraries (*.a), and I want to build a shared library (*.so) to link against those static libraries (*.a). How can I do so in gcc/g++? You can (just extract all the .o files and link them with -shared to make a .so ), but whether it works, and how well it works, depends on the platform and whether the static library was compiled as position-independent code (PIC). On some platforms (e.g. x86_64), non-PIC code is not valid in shared libraries and will not work (actually I think the linker will refuse to make the .so ). On other platforms, non-PIC code will work in

I used gdb normally until this week. Now running gdb I see: (gdb) r Starting program: /Volumes/MyProg dyld: Library not loaded: @rpath/libCore.so Referenced from: /Volumes/MyProg Reason: image not found (gdb) How to fix it? I have: OSX 10.9 GNU gdb (GDB) 7.6 installed with MacPorts P.S. I have reinstalled gdb and Xcode. This does not help. I see a lot of questions about dyld issues, but obviously I lack experience with libraries on OSX, and they appears to be useless for me. For example this topic: dyld issues library not loaded But how to download library again? Or this topic: Dyld: Library

I am maintaining a small application that has some plugin-like functionality, which is implemented through runtime-loaded dynamic modules. Specifically, since it's a Gtk+ app, I'm using gmodule, but the question applies to dlfcn.h / dlopen() based dynamic library loading just as well. My main program has a single, global struct variable holding some global information. I want this information to be available to functions defined in the dynamically loaded plugins. On Linux, I could just refer to this global variable directly - this works well, and I'm guessing that gcc or the linker take care

I have a more general question on working with libraries on with Xcode when building iPhone apps. I've created a framework from a project I've been working on to use some parts of it in other apps. That works pretty good, so far. But I have no idea how to debug into the files included in the included framework. I hope to get some kind of 'best practice' on that. Thanks a lot –f There have been a lot of discussions of how best to reuse code with static libraries. I've settled on the method described here by Clint Harris (which I think is what Shawn is suggesting as well). Creating a project

While I was studying about shared library I read a statement Although the code of a shared library is shared among multiple processes, its variables are not. Each process that uses the library has its own copies of the global and static variables that are defined within the library. I just have few doubts. Whether code part of each process are in separate address space? Whether shared-library code part are in some some global(unique) address space. I am just a starter so please help me understand. Thanks! Shared libraries are loaded into a process by memory-mapping the file into some portion