[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: testing with .so
From: |
Waldemar Rosenbach |
Subject: |
Re: testing with .so |
Date: |
Mon, 05 Aug 2002 14:41:01 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204 |
Alexandre Duret-Lutz wrote:
"Waldemar" == Waldemar Rosenbach <address@hidden> writes:
[...]
Building this kind of wrapper is actually the job
of Libtool; you should be able to run `./test' directly if you
pass the `.la' file on the test_LDADD line.
Although it works, I don't want "test" to be linked with the library,
but dlopened by it.
I need something like
test_LDFLAGS = -R`pwd`/.libs
or
test_ADDRPATH = .
so the library is found when the test is run.
Is this possible without libltdl and without explicitly specifying the
.libs directory?
VPATH = ${srcdir}
TESTS = test
check_LTLIBRARIES = libTestAction.la
check_PROGRAMS = test
test_SOURCES = test.cpp
libTestAction_la_SOURCES = \
testaction.cpp\
testaction.h\
init.cpp\
init.h
#test_LDADD = ../libFiniteStateMachine.la libTestAction.la
test_LDADD = ../libFiniteStateMachine.la
libTestAction_la_LIBADD = ../libFiniteStateMachine.la
libTestAction_la_LDFLAGS = -rpath
/dummy_path/so_libtool_builds_a_shared_lib -module
test_LDFLAGS = -R`pwd`/.libs
#test_LDFLAGS = -rpath `pwd`/.libs