|
|
Blitz Devel : |
From: Julian C. Cummings (cummings_at_[hidden])
Date: 2004-05-03 14:25:44
Hi Theo,
> -----Original Message-----
> From: blitz-dev-bounces_at_[hidden]
> [mailto:blitz-dev-bounces_at_[hidden]] On Behalf Of
> Theodore Papadopoulo
> Sent: Monday, May 03, 2004 5:49 AM
> To: blitz-dev_at_[hidden]
> Subject: [Blitz-dev] Compilation problems...
>
>
>
> Contrarily, to what has been assumed in a message (Julian I believe
> it was you, but I may be wrong), the $(top_builddir) in several
> Makefile.am are useful for people willing to compile in separate
> directory !!! Thus they should be put back...
The specific change that I made was in the -I include file search directory
options that are used to build the blitz library and example codes. These
used to be $(top_srcdir) and $(top_builddir), and I changed it to $(srcdir)
and $(top_srcdir). If I remember right, I made this change because I was
running into problems in the case where the --prefix option is not used and
the user is just building blitz locally. I'm not an expert on automake and
autoconf, but from what I read in the online manuals, it seems like
searching the source directories is the right way to find header files,
whereas the build directories would be used to locate compiled object files
for archiving or linking. As long as you use a version of make that
supports the VPATH construct (such as GNU make), you should be able to
compile multiple versions of blitz in separate directories with no problems.
This is discussed briefly in the autoconf manual. If you could, please send
a specific instance of how you configure blitz to compile in a separate
directory and how the current Makefile configuration fails. What are the
variables $(top_srcdir) and $(top_builddir) being converted to in your case?
I'm sure there is a way to make this work properly.
Regards, Julian C.
Dr. Julian C. Cummings
Staff Scientist, CACR/Caltech
(626) 395-2543
cummings_at_[hidden]