Re: Problems with commonc++ 1.2.6

[Shawn McKenney]

Yes, the docs would get built, but that is not the desired behavior. 
The source directory should remain pristine when building in a build
directory.  Everything should be built _against_ the source directory
and _into_ the build directory.

Shawn


On Fri, 2004-11-19 at 05:42, David Sugar wrote:
> I thought of a slightly different solution:
> 
> Replacing the $(DOXYGEN) Doxyfile in the Makefile.am with something like:
> 
>     (cd @srcdir@/doc ; $(DOXYGEN) Doxyfile)
> 
> The idea being to make sure doxygen is always executed from within the 
> primary source directory tree rather than the build directory tree.
> 
> Shawn McKenney wrote:
> 
> >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
> >>    
> >>
> >
> >  
> >
-- 
====================================
Shawn McKenney
Los Alamos National Laboratory, P-25
505 667 3277
====================================