* Paulo J. Matos wrote on Fri, May 12, 2006 at 03:01:55PM CEST:
> On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
> >
> >Ah, that's most probably what I need. Thanks a lot!
I don't know if you _need_ a convenience archive. You should not link
it into two different shared libraries that one
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Ah, that's most probably what I need. Thanks a lot!
After reading the chapter you mentioned and browsing the rest of the
very nice book I implemented things that way and set up the structure
(I'll forget lib2):
tree
|- lib
||- install
On 12/05/06, Warren Young <[EMAIL PROTECTED]> wrote:
Paulo J. Matos wrote:
>
> I've created liblogger basically as a new project with configure.ac
> and Makefile.am, etc. It builds ok and then I added to Makefile.am of
> both lib1 and lib2:
> lib1_la_LIBADD = ../../liblogger/src/liblogger.la
Act
Paulo J. Matos wrote:
I've created liblogger basically as a new project with configure.ac
and Makefile.am, etc. It builds ok and then I added to Makefile.am of
both lib1 and lib2:
lib1_la_LIBADD = ../../liblogger/src/liblogger.la
Actually, what I was suggesting is that you build and _install_
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
Now it is making liblogger before but still I get the same nasty error
from make. :-(
make[2]: *** No rule to make target
`../../liblogger/src/liblogger.la', needed by `lib1.la'. Stop.
Argh, it should be ../../../liblogger/src/liblogger.l
On 12/05/06, Paulo J. Matos <[EMAIL PROTECTED]> wrote:
How can I do that? I don't think I ensured that.
Hi, I just changed lib1/Makefile.am to:
SUBDIRS = ../../liblogger src
Now it is making liblogger before but still I get the same nasty error
from make. :-(
make[2]: *** No rule to make ta
On 12/05/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
Hi Paulo,
* Paulo J. Matos wrote on Fri, May 12, 2006 at 12:22:59AM CEST:
>
> I've created liblogger basically as a new project with configure.ac
> and Makefile.am, etc. It builds ok and then I added to Makefile.am of
> both lib1 and lib2:
Hi Paulo,
* Paulo J. Matos wrote on Fri, May 12, 2006 at 12:22:59AM CEST:
>
> I've created liblogger basically as a new project with configure.ac
> and Makefile.am, etc. It builds ok and then I added to Makefile.am of
> both lib1 and lib2:
> lib1_la_LIBADD = ../../liblogger/src/liblogger.la
>
>
On 11/05/06, Warren Young <[EMAIL PROTECTED]> wrote:
Paulo J. Matos wrote:
> I see two ways: Creating yet another library and then link it with
> lib1 and lib2 and later link to the main code lib1, lib2 and
> liblogger.
That's what I do.
Thanks for all your replies. I followed your advice and
Paulo J. Matos wrote:
I see two ways: Creating yet another library and then link it with
lib1 and lib2 and later link to the main code lib1, lib2 and
liblogger.
That's what I do.
It's really no different than linking your programs to, for instance,
the GNOME libraries, which just happen to u
i would guess that you would have the logger be lib3 in the lib folder.
On Wed, 10 May 2006, Paulo J. Matos wrote:
> Hi all,
>
> I have a source tree, which is maintained with autotools. It goes
> something like this:
> MySoftware
> |- lib
>|- lib1
>|- lib2
> |- src
>
> lib1 a
Hi all,
I have a source tree, which is maintained with autotools. It goes
something like this:
MySoftware
|- lib
|- lib1
|- lib2
|- src
lib1 and lib2 are compiled and then linked to the src software.
However, I've just developed a logger utility interface which uses
log4cpp and I w
12 matches
Mail list logo
