On Sunday 30 March 2003 12:57, Dr. David Kirkby wrote:
[...]
> Secondly, if it is sensible, how would I do it? Can I add a target
> like 'benchmark' and if so how? Clearly any such target would need to
> depend on the fact the sources have already been built. I could write
> the benchmark as a scri
On Sunday 16 February 2003 01:46, Bob Rossi wrote:
[...]
> Is there any way to solve my problem? Help would be greatly appreciated.
Hello Bob,
I would do it in this way, but I'm not an Autotools expert and it requires
Libtool:
top_src_dir
configure.ac
[...]
Hello,
SWIG generates a Python module for me. This works fine with Automake 1.7
except that a 'make distcheck' fails:
No files given to ../config/py-compile
make[2]: *** [install-nodist_pythonPYTHON] Error 1
I suppose this is because the generated Python file is in the build directory
and not i
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.
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 pas
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 \
$(top_s
Hello,
I used to generate my Doxygen documentation generation this way (Makefile.am):
EXTRA_DIST = @PACKAGE@.doxygen.in
CLEANFILES = *.html *.gif *.css
noinst_PROGRAMS = index.html
index_html_SOURCES = @PACKAGE@.doxygen
index.html: @PACKAGE@.doxygen
doxygen @PACKAGE@.doxygen
But with
