[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Building Secondary Modules
- From: "Antonio Scuri" <scuri@...>
- Date: Wed, 23 Jun 2010 10:02:22 -0300
I have two modules. One is straight forward to build. But the second one
depends on C functions that were implemented in the first module.
So when linking the second module in Linux I have to add the first module
using "-lmodule1". But it fails, because the first module is called
"module1.so" and not "libmodule1.so".
I know there are "alternative" solutions, like creating a symbolic link
(but do I have to distribute the link? I check using ldd that it depends on
the link, not to the actual file. Ugly...), or use standard names and change
the LUA_CPATH (like I do in IUP). Or even build a base library to store
those functions and link both libraries to that library, but that's nonsense
just to store a couple of functions.
So I would like to know if there are other solutions. I searched the Wiki
with no success.