Shared Object Question


 
Thread Tools Search this Thread
Top Forums Programming Shared Object Question
# 8  
Old 03-02-2011
Quote:
Originally Posted by dorik
Nope, just a class declaration. When I had it working by including the definitions in the project and the library, I set the static variable in the project and didn't set it in the library.
I really don't think you can make one member of a class be exported from the code into the library, and the rest exported from the library to the code. The whole thing gets instantiated as one 'thing'.

It might work if you make it a global variable instead of a member, but you'll have to do it backwards from the rest of the library: In the shared library, it'll be an extern "C" whatever *variable; and in your library-using code it's extern "C" { whatever *variable=stuff; } That'd definitely work with static linking. Dynamic I'm less sure: It might demand that the variable actually exists to be able to create the shared library.

Quote:
Instead of including the definitions in both, I'd like to try the other approach I mentioned (exporting dynamic symbols in the project).
That exports your code's symbols. Not the universe.

You might just have to add a call to set the static member.

Last edited by Corona688; 03-02-2011 at 12:03 PM..
This User Gave Thanks to Corona688 For This Post:
# 9  
Old 03-02-2011
Quote:
I really don't think you can make one member of a class be exported from the code into the library, and the rest exported from the library to the code.
Yep, that's why I want to take the base class cpp file (which has the static menber) out of the library since it's also in the main app.

Here's how it's set up: In the project I have a base class header and cpp. In the library I have a subclass header and cpp. The library also includes the base class header. It doesn't have the base class definition, which I want to be resolved when the library is loaded in.

Earlier, I was adding in the base class cpp to the library (plus whatever else it needed). But I did some research and it seems I don't need to include all those definitions in both. As one site puts it:

(Sorry, I have to mangle this url because I'm not allowed to post links yet)

www
.informit.
com/articles
/article.aspx?p=22435&rll=1:

Quote:
A shared library may also contain references to functions and variables that aren't themselves defined in the shared library
...
If your main executable exports any dynamic symbols (as if it were a shared library), these symbols may be used.
Since I took unnecessary definitions outside of the library the library hasn't even been loading. If I can get it to load, I am hoping that static member won't be duplicated.

Edit: Just to make sure we're using the same terms: by definition I mean cpp and by declaration I mean header.

Last edited by dorik; 03-02-2011 at 12:31 PM..
# 10  
Old 03-02-2011
Quote:
Originally Posted by dorik
Since I took unnecessary definitions outside of the library the library hasn't even been loading.
They would seem to be necessary, then. Remember that exporting dynamic symbols from your project exports your symbols, not the entire universe...

Also make sure your library isn't last in the link order, the stuff you want it to link to should come after it. I'm not sure that'll help, but sometimes that matters for static linking...
Quote:
If I can get it to load, I am hoping that static member won't be duplicated.
I don't think it works that way for the reasons I stated above.
Quote:
Edit: Just to make sure we're using the same terms: by definition I mean cpp and by declaration I mean header.
The compiler doesn't know any difference between header files and source files. What matters is what you put in them. So it's entirely possible for the wrong kind of declaration in a header file to create many conflicting symbols when included in several files.

I don't suppose you could reduce this to a minimal example?
# 11  
Old 03-02-2011
Sure, I'll try to post a sample by tomorrow.

Quote:
Also make sure your library isn't last in the link order, the stuff you want it to link to should come after it.
The library is being loaded at runtime using dlopen().
# 12  
Old 03-03-2011
Quote:
Originally Posted by dorik
The library is being loaded at runtime using dlopen().
I really think you're going to have to link in the libraries you need when you create the library, then.
# 13  
Old 03-03-2011
Hi Corona688,

I made a simple example and it works. When you create a library, you do not need definitions that are also in the main app since they can be resolved when the object is loaded.

Main App: BaseClass.h, BaseClass.cpp, OtherClass.h, OtherClass.cpp, main.cpp
Shared Library: ChildClass.h, ChildClass.cpp, BaseClass.h, OtherClass.h

Note: I included OtherClass to show that the definition did not need to exist in the shared library.

BaseClass.h
Code:
#ifndef BASE_CLASS_H
#define BASE_CLASS_H

#include <string>
#include "OtherClass.h"

using std::string;

class BaseClass
{
public:
    static int val;

    BaseClass();
    virtual ~BaseClass(); 
    
    virtual string getString() = 0;

private:
    
};

#endif

BaseClass.cpp
Code:
#include "BaseClass.h"

int BaseClass::val = 5;

BaseClass::BaseClass()
{
}

BaseClass::~BaseClass()
{
}

ChildClass.h
Code:
#ifndef CHILD_CLASS_H
#define CHILD_CLASS_H

#include "BaseClass.h"

class ChildClass : public BaseClass
{
public:
    ChildClass();

    string getString();
};

extern "C" BaseClass * create();

#endif

ChildClass.cpp
Code:
#include "ChildClass.h"

ChildClass::ChildClass(): BaseClass()
{
    OtherClass oc(4);
    oc.getValue();
}

string ChildClass::getString()
{
    return "child class";
}

BaseClass * create()
{
    return new ChildClass();
}

OtherClass.h
Code:
#ifndef OTHER_CLASS_H
#define OTHER_CLASS_H

class OtherClass
{
public:
    OtherClass(int value);
    int getValue();

private:
    int value;
};

#endif

OtherClass.cpp
Code:
#include "OtherClass.h"

OtherClass::OtherClass(int value)
{
    this->value = value;
}

int OtherClass::getValue()
{
    return value;
}

main.cpp
Code:
#include "BaseClass.h"

#include <iostream>
#include <dlfcn.h>

using std::cout;
using std::endl;

int main()
{
    typedef BaseClass * (*CreateFunc)();

    void *handle = dlopen("./libsltest.so.1.0", RTLD_NOW);
    if (handle)
    {
        cout << "loaded library" << endl;
        CreateFunc cf = (CreateFunc)dlsym(handle, "create");
        
        if (cf)
        {
            cout << "loaded create function" << endl;
            BaseClass *b = cf();
            cout << b->getString() << endl;
            dlclose(handle);

            cout << BaseClass::val << endl;
            cout << b->val << endl;
        }
        else
        {
            cout << "could not load create function" << endl;
        }
    }
    else
    {
        cout << "could not load library" << endl;
    }
    
    return 0;
}

The static values are the same, as expected.

In the project where I'm getting unresolved errors, I'm using Qt to make the shared library. The problem could be there. I'll post again if I have any leads.

Thanks for your help,
-- Derek
# 14  
Old 03-04-2011
I'm not sure what this code is supposed to prove, since it's not doing anything remotely like what you've described your actual project trying to do.

You can export your own symbols into the library. You can't export something else's symbols. How can you possibly export something you never have? These dependencies remain unresolved up until runtime!

You do seem to be able to have a library import your definition of a static member, much to my surprise. So if it's complaining about being doubly defined, that's because it is. Take the extra definition out of your library.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

Help building and using a shared object (x64)

Hello, I am not that experienced with Linux, and I am currently facing some issues. The application I'm working on uses hundreds of threads. To optimize the memory usage, I am putting all my data inside a shared object (so). The steps for this are as follows: 1. a C file (generated... (17 Replies)
Discussion started by: Maelstrom
17 Replies

2. Red Hat

shared object

Hi, I would like to create a shared object ( .so). This shared object 1. uses the functions from a library. 2. Also it should be able to use the global variable in an app To achieve this what should I do ? 1) To use the functions in the library should I give the -ld option while... (1 Reply)
Discussion started by: rvan
1 Replies

3. Programming

Error while running shared object

Hello, While running a c++ shared object on AIX I am facing below error - rtld: 0712-001 Symbol __ct__3ETDFv was referenced from module /bancs/aml/lib/libmonitor.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol etd_insert__3ETDFv was... (3 Replies)
Discussion started by: yatrik007
3 Replies

4. AIX

AIX 5.2 C++ shared object issue

Hi all, I am developing an application with two components. One "c" binary and one "C++" shared object. While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly. I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies

5. Shell Programming and Scripting

Any way to access shared object using shell

Hi, I have created a shared object (abc.so) which has a function sum(int a, int b). Is there any way to load the "abc.so" and use the sum function using shell script.. thanks in advance (2 Replies)
Discussion started by: yhacks
2 Replies

6. UNIX for Advanced & Expert Users

Issue with shared object in AIX

Hi All, I have a problem with the shared objects setup in AIX. We have a customized shell written by the developers over here. When i issue a MQ Series command (mqsilist) it is giving the error as . All the commands making use of this libImbCmdLib.a.so is failing. But when executed in normal... (1 Reply)
Discussion started by: dhanamurthy
1 Replies

7. Programming

calling a shared object from a daemon

Hi I have a multithreaded daemon(server) which will accept connections from various clients and sends back results to them. In order to serve my daemon clients, it has to establish a TCP connection to another server(vendor supplied which is listening on a specific TCP port) and gets the... (11 Replies)
Discussion started by: axes
11 Replies

8. AIX

Shared Object library problem

Hi, When using shared objects on AIX 4.3 i am getting runtime problems. I have a small sample program which links to a shared object libray, oracle and system related libraries. At runtime it fails (gives segmentation fault and coredump ) in one proc file when executing login statement. But... (0 Replies)
Discussion started by: suman_jakkula
0 Replies

9. Linux

Shared Object File

Hi All, I created the share object file using gcc -shared -fpic mypp.cpp -o myp.so but, pls tell me how to link this .so file to my client program. Thanks (0 Replies)
Discussion started by: sarwan
0 Replies

10. Programming

Does my ld support shared object creation

Hi, I have been trying to create a sharef object on my HP UX 11 machine (HP-UX <myhostname> B.11.00 A 9000/879 ...... two-user license) to create the shared object first I am creating the object file using cc -Aa -c +z dyn.c (I use -Aa and +z as per HP's manual on linkers ) to create the... (0 Replies)
Discussion started by: linuxpenguin
0 Replies
Login or Register to Ask a Question