[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Wed, 23 Oct 2002 18:00:23 +0200
I'm working on linux based embedded platforms. To build a complete
platform, we usually compile and install our software packages in a
directory that is specific to each developer, say:
Then, the compiled libraries and executables that must be actually
available on the final platform are manipulated so that they finally
...when the platform has booted.
Here comes the problem:
- Scenario 1: a library (let say glib) is configured with the final
prefix (/usr) and installed for instance with a make install
Then, a program that uses the library will link with sth like
Unfortunately, libtool (1.4.2a) will transform this into...
Grr. This is not a library compiled for the same architecture.
- Scenario 2: the library is directly configured to get installed in
Then, the linking will be performed correctly, but a wrong rpath
will be added in the executable...
Do you know a better method ?
Frédéric Gobry SMARTDATA
Software Engineer Lausanne - Switzerland
+41 21 693 84 98
Description: PGP signature
- library relocation,
Frederic Gobry <=