doing "scons doc" builds the kernel libraries and python wrapper which it would be nice to avoid as those can take a long while on a laptop. I loose the dependency trail at build/include :-)
Daniel Russel wrote: > doing "scons doc" builds the kernel libraries and python wrapper which > it would be nice to avoid as those can take a long while on a laptop. > I loose the dependency trail at build/include :-)
Right, because that's asking to build everything in the doc/ directory. doc/examples/ needs the kernel built first so that it can actually run the examples. If you only want to build part of the documentation, try 'scons doc/html' or 'scons doc/internal'.
Ben
Good point. Thanks.
On Sep 24, 2008, at 1:33 PM, Ben Webb wrote:
> Daniel Russel wrote: >> doing "scons doc" builds the kernel libraries and python wrapper >> which >> it would be nice to avoid as those can take a long while on a laptop. >> I loose the dependency trail at build/include :-) > > Right, because that's asking to build everything in the doc/ > directory. > doc/examples/ needs the kernel built first so that it can actually run > the examples. If you only want to build part of the documentation, try > 'scons doc/html' or 'scons doc/internal'. > > Ben > -- > ben@salilab.org http://salilab.org/~ben/ > "It is a capital mistake to theorize before one has data." > - Sir Arthur Conan Doyle > _______________________________________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/listinfo/imp-dev
How do we force it to rebuild the api documentation? It might be fine just have that be built every time you build the documentation if there is no way to get the dependencies right? Thanks.
Also, really doc/examples should only be built when tests are run. Not sure how easy that is to implement though.
Thanks.
On Sep 24, 2008, at 1:33 PM, Ben Webb wrote:
> Daniel Russel wrote: >> doing "scons doc" builds the kernel libraries and python wrapper >> which >> it would be nice to avoid as those can take a long while on a laptop. >> I loose the dependency trail at build/include :-) > > Right, because that's asking to build everything in the doc/ > directory. > doc/examples/ needs the kernel built first so that it can actually run > the examples. If you only want to build part of the documentation, try > 'scons doc/html' or 'scons doc/internal'. > > Ben > -- > ben@salilab.org http://salilab.org/~ben/ > "It is a capital mistake to theorize before one has data." > - Sir Arthur Conan Doyle > _______________________________________________ > IMP-dev mailing list > IMP-dev@salilab.org > https://salilab.org/mailman/listinfo/imp-dev
Daniel Russel wrote: > How do we force it to rebuild the api documentation? It might be fine > just have that be built every time you build the documentation if > there is no way to get the dependencies right? Thanks.
The doxygen builder does have the correct dependencies, but scons always thinks directory targets are up to date if they exist. I will "fix" the doxygen builder in the same way as the docbook and epydoc builders to work around this problem. For now you can force a rebuild with "rm -rf doc/internal/html".
Ben
On Sep 24, 2008, at 4:23 PM, Ben Webb wrote:
> Daniel Russel wrote: >> How do we force it to rebuild the api documentation? It might be fine >> just have that be built every time you build the documentation if >> there is no way to get the dependencies right? Thanks. > > The doxygen builder does have the correct dependencies, but scons > always > thinks directory targets are up to date if they exist. I will "fix" > the > doxygen builder in the same way as the docbook and epydoc builders to > work around this problem. For now you can force a rebuild with "rm -rf > doc/internal/html". Ahhh, thanks.
participants (2)
-
Ben Webb -
Daniel Russel