shared-libraries

I am developing a shared library using C++ under Linux, and I would like this library to use log4cxx for logging purposes. However, I'm not sure how to set this up. For log4cxx to work, I need to create a logger object. How can I make sure this object is created when my library is loaded? I suspect that it will be easiest to create the logger object as a global variable and then use it from any of the source files of my library, declaring it as extern in the headers. But how can I have the logger created automatically once an application connects to the library? I know that in DLLs for Windows

Does a C++ shared library have its own memory space? Or does it share the caller process' one? I have a shared library which contains some classes and wrapper functions. One of this wrapper function is kinda: libXXX_construct() which initializes an object and returns the pointer to the said object. Once I use libXXX_construct() in a caller program where is the object placed?Is it in the "caller" memory space or is it in the library's memory space? A linked instance of the shared library shares the memory space of the instance of the executable that linked to it, directly or indirectly. This is

Is there any way to know which functions are exported from the dll through python foreign function library ctypes ? And if possible to know details about the exported functions through c types . If yes, could someone provide a snippet of code? I don't think ctypes offers this functionality. On Windows with visual studio: DUMPBIN -EXPORTS XXX.DLL Or for mingw on windows: objdump -p XXX.dll xealits If you are on Linux, there is a handy utility nm to list the content of a shared library (there is always a handy utility on Linux, especially for C stuff). Here is the question about it. You use it

I have a question on shared libraries vs static libraries loading time. Assume that i have a executable foo.exe which uses liba, libb, libc. Also at a given time there are more than 10 instances of the executable running on the machine. Now if the above 3 libraries were shared libraries : 1st Insance is loaded into RAM : The time taken will be time taken by main() of foo.exe to be loaded memory (assuming its negligible) + time to load liba + time to load libb + time to load libc 2nd instance is started : Now assume a second instance of this executable is run. Since all libraries are already

We're developing an application that will have a plug-in "architecture" to allow consumers of the app to provide their own proprietary algorithms. (We will basically have a set of parsers and allow third parties to provide their own as well) The domain space requires very high performance, so out-of-process bindings are not going to work and we'd rather leave the heavyweight things like CORBA and COM alone. Basically we're looking for a simple cross-platform wrapper around: load library from a relative path provide a mapping of the particular dll/.so to some configuration/name do some

For VC, I can write a DEF file and use the 'NONAME' directive to leaving only the ordinal number in dll's export table. How could I do the same thing with gcc and ELF format shared library? Or, is there something equivalent in ELF shared library like the ordinal number in a PE format DLL? If not, how could I hide the exported symbol's name within a shared library? ====================================== UPDATE: Some additional descriptions: In Windows, you can export a function by only place a integer ID (the ordinal) with an empty name. To show it, the normal layout for a dll's export table

I'm working on a Firefox plugin that uses external libraries to render 3D graphics on the browser. The problem is that I want the plugin to use external libraries packed with it without changing the LD_LIBRARY_PATH variable. The libraries are installed in a position relative to the plugin (a shared library too), while the actual executable (i.e. the browser) can be located somewhere entirely else. I'm testing it on Ubuntu (no problem at Windows version of the plugin) My dependencies are OpenSceneGraph libraries and static compilation will make the plugin really big (not an option if there is