GNOME Bugzilla – Bug 656388
documentation not generated if source is in /build directory
Last modified: 2011-08-12 17:54:28 UTC
Hi, I have a (generated) doxy.conf file with the input field looking like: INPUT = /build/bigon-libssh_0.5.1-1-amd64-MNB3nS/libssh-0.5.1/include/libssh \ /build/bigon-libssh_0.5.1-1-amd64-MNB3nS/libssh-0.5.1/src \ /build/bigon-libssh_0.5.1-1-amd64-MNB3nS/libssh-0.5.1/doc For some reasons the documentation is never generated. After trouble shooting, I figured out that if I moved my source directory to a "shorter" path and adjusted the INPUT that the documentation was build properly.
Doxygen imposes no artificial limits on the input parameter length. Maybe the OS/filesystem imposes some limits. Can you provide a self contained example (source+config file in a zip or tar) that allows me to reproduce the problem? Also mention the OS + filesystem you use.
turning QUIET flag to NO, I see: Searching for files in directory /build/bigon-libssh_0.5.1-1-amd64-Wifblp/libssh-0.5.1/include/libssh Searching for files in directory /build/bigon-libssh_0.5.1-1-amd64-Wifblp/libssh-0.5.1/src Searching for files in directory /build/bigon-libssh_0.5.1-1-amd64-Wifblp/libssh-0.5.1/doc Reading and parsing tag files Building group list... In a normal run I have the list of files added after "Reading and parsing tag files" The debian pkg I'm trying to build is http://packages.qa.debian.org/libs/libssh.html and the upstream source can be found at http://www.libssh.org/files/0.5/ I've managed to rename the directory "/build" to "/blahblah" and the generation is working again.... so this is not actually a path length limit
Thanks for the additional information, but unfortunately it didn't answer my questions, and I still have no clue how I can reproduce the problem. Running doxygen on the upstream tarball did not reveal anything strange.
Just tried again (outside of any autobuilder) on my natty machine. create a /build directory and put the libssh-0.5.1 directory into it and make the necessary step to generate the doc (-> the doc is not complete and index.html is empty) rename the /build directory to something else (/blahblah) do it again (-> more files generated and the documentation seems more complete)
Since it seems difficult for you to describe a reproduction scenario, how about this: wget http://www.libssh.org/files/0.5/libssh-0.5.1.tar.gz mkdir build cd build tar zxvf ../libssh-0.5.1.tar.gz cd libssh-0.5.1 doxygen -s -g (cat Doxyfile ; echo "INPUT=doc src include" ) | doxygen - For me this seems to give correct output (i.e. no empty index.html)
mkdir /build cd /build wget http://www.libssh.org/files/0.5/libssh-0.5.1.tar.gz tar zxvf libssh-0.5.1.tar.gz cd libssh-0.5.1 mkdir builddir cd builddir cmake /build/libssh-0.5.1 make doc This is not working, however: mkdir /blah cd /blah wget http://www.libssh.org/files/0.5/libssh-0.5.1.tar.gz tar zxvf libssh-0.5.1.tar.gz cd libssh-0.5.1 mkdir builddir cd builddir cmake /blah/libssh-0.5.1 make doc Is working
you can replace "make doc" by "doxygen doc/doxy.conf" same result
ah, this explains things: EXCLUDE_PATTERNS = */.git/* \ */.svn/* \ */cmake/* \ */build/* i.e. all directories that have /build/ as part of the path are excluded... So this is a configuration error, not a bug in doxygen.