Re: Problems with commonc++ 1.2.6

[Shawn McKenney]

My problem was a little different, but it may be related (our output
looked very similar).  Because I have to build commonc++ on several
platforms, and I want to use the same source directory, I always build
it in a separate build directory.

i.e.:
> tar -zxvf commoncpp2-1.2.6.tar.gz
> mkdir build1
> cd build1
> ../commoncpp2-1.2.6/configure && make

However, the doc/Makefile.am wasn't finding Doxyfile, and the build was
failing.  Modifying doc/Makefile.am helped the compilation, but doxygen
still wasn't finding the input files to create proper documentation (I
didn't notice this because I use the source code and not the docs).  The
(new) solution that worked for me was to have ./configure generate
Doxyfile (from Doxyfile.in) with the correct paths of the input files
and leave doc/Makefile.am alone.

Maurizio, this may or may not solve your problem, as ours seem somewhat
different.  Remember to run ./reconfig after applying the attached path
with:

commoncpp2-1.2.6> patch -p1 </path/to/commoncpp2-1.2.6-doxygen-1.patch

(BTW, the other patch should be removed, as Doxyfile will exist in
@builddir@ now instead of in @srcdir@)

Hope this helps -
Shawn

On Thu, 2004-11-18 at 11:22, David Sugar wrote:
> I attached the log that I get.  Maybe something obvious will be spotted 
> by comparing the two...
-- 
====================================
Shawn McKenney
Los Alamos National Laboratory, P-25
505 667 3277
====================================

commoncpp2-1.2.6-doxygen-1.patch
Description: Text Data