Hi
for a new project with autotools I'm using libraries not in standard
directories; at configure time I pass the right arguments, but when I run
make distchek
it all fails: how can I pass arguments in this case?
thanks in advance
Lorenzo
--
Lorenzo Bettini, PhD in Computer
On Fri, 12 Dec 2008, Lorenzo Bettini wrote:
for a new project with autotools I'm using libraries not in standard
directories; at configure time I pass the right arguments, but when I run
make distchek
it all fails: how can I pass arguments in this case?
Supply any needed arguments via
Hi Bob, Lorenzo,
* Bob Friesenhahn wrote on Fri, Dec 12, 2008 at 07:14:36PM CET:
On Fri, 12 Dec 2008, Lorenzo Bettini wrote:
for a new project with autotools I'm using libraries not in standard
directories; at configure time I pass the right arguments, but when I
run
make distchek
it
On Fri, 12 Dec 2008, Ralf Wildenhues wrote:
Supply any needed arguments via DISTCHECK_CONFIG_FLAGS.
Typo? That would be DISTCHECK_CONFIGURE_FLAGS.
Ahhh, it is working due to this in my Makefile.am:
DISTCHECK_CONFIGURE_FLAGS=$(DISTCHECK_CONFIG_FLAGS)
The loop is now closed. :-)
Bob
Tom == Tom Tromey [EMAIL PROTECTED] writes:
[...]
Tom You could write:
Tom top_dir = ..
Tom foo_SOURCES = $(top_dir)/foo.c
Hmmm, are you sure? This construct is the one used in PR/325.
It breaks the dependency tracking code (the dependency file will have
\$\(top_dir\) in its name).
--
adl == Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
Tom top_dir = ..
Tom foo_SOURCES = $(top_dir)/foo.c
adl Hmmm, are you sure? This construct is the one used in PR/325.
adl It breaks the dependency tracking code (the dependency file will have
adl \$\(top_dir\) in its name).
Yeah, you're
On Wednesday 25 September 2002 15:56, you wrote:
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
I know in the past it didn't work to put `$(top_srcdir)' in a path in
a _SOURCES variable. Alexandre, has this changed?
I don't think this would cause your problem necessarily, but
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
Sebastian ok, changing `$(top_srcdir)' to `..' fixed the problem, but
Sebastian is this a temporay workaround or is the behaviour of the
Sebastian dist rule not correct in this case? To use $(top_srcdir)
Sebastian instead of '..' seems more
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
Sebastian Why are these files in the build directory?
No idea, sorry. Could you send a bug report?
--
Alexandre Duret-Lutz
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
Sebastian libTACOExtensions_la_SOURCES = $(top_srcdir)/server/src/TACOServer.cpp \
I know in the past it didn't work to put `$(top_srcdir)' in a path in
a _SOURCES variable. Alexandre, has this changed?
I don't think this would cause
Tom == Tom Tromey [EMAIL PROTECTED] writes:
[...]
Tom I know in the past it didn't work to put `$(top_srcdir)' in a path in
Tom a _SOURCES variable. Alexandre, has this changed?
Not to my knowledge. The issue I remember is PR/325.
[...]
--
Alexandre Duret-Lutz
Hello!
On Wednesday 25 September 2002 11:13, Tom Tromey wrote:
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
Sebastian libTACOExtensions_la_SOURCES =
$(top_srcdir)/server/src/TACOServer.cpp \
I know in the past it didn't work to put `$(top_srcdir)' in a path in
a _SOURCES
Sebastian == Sebastian Huber [EMAIL PROTECTED] writes:
I know in the past it didn't work to put `$(top_srcdir)' in a path in
a _SOURCES variable. Alexandre, has this changed?
I don't think this would cause your problem necessarily, but it is an
oddity.
This is definitely the problem.
Hello,
in a 'lib' directory I have the following Makefile.am:
lib_LTLIBRARIES = libTACOExtensions.la
libTACOExtensions_la_SOURCES = $(top_srcdir)/server/src/TACOServer.cpp \
$(top_srcdir)/common/src/TACOException.cpp \
$(top_srcdir)/common/src/TACOExtensions.cpp \
14 matches
Mail list logo
