Hi J-S On Wed, Dec 17, 2008 at 2:08 AM, Jean-Sébastien Guay <[email protected]> wrote: > Hi Mattias, > >> stop.stop :) >> Ignore those. You don't need any of them. What happens is that the >> Documentation.cmake issues find_package(UnixCommands) among other >> things. What's important is that it finds doxygen and then you need to >> help it find dot. > > OK, and I assume Documentation.cmake is a file that comes with CMake, or > else you (or someone else) would have fixed that (i.e. either hidden the > useless settings or not issued find_package(UnixCommands) ). Is that right?
yep. On windows it don't make sense to look for the UnixCommands (in this case). It makes sense on unices. > >> one of the old doxyfiles that I updated included the source >> (doc/Doxyfiles/all_Doxyfile). That file now gets processed to >> <builddir>/doc/all_Doxyfile. I didn't create targets for these >> doxyfiles as I wasn't sure if they were used at all. > > I didn't get that. Do you mean that CMake will take whatever settings were > in the doc/Doxyfiles/all_Doxyfile file, adjust the dot path and such, and > then save the result to <builddir>/doc/all_Doxyfile? So if I make changes to > doc/Doxyfiles/all_Doxyfile they should be kept in > <builddir>/doc/all_Doxyfile? yes. You are correct. We previously used one of the doxyfiles in doc/Doxyfiles. When I updated that file I noticed that there were some regular plain old doxyfiles sitting in that directory. I wanted to update them or remove them. Robert wanted them to stay so I promoted them to cmake scripts and added processing of them in the CMakeLists.txt. I didn't add any targets for them on Roberts suggestion. > >> So you can do : >> doxygen <builddir>/doc/all_Doxyfile >> this wil doxyprocess the src recursively > > I could also probably modify the <builddir>/doc/openscenegraph.doxyfile > (knowing my changes will be lost the next time I run CMake...) and then > build the docs from Visual Studio which should use my modified file... What you want is not something I usually do so it didn't occur. I was busy creating openscenegraph-doc packages :-) > > IMHO, it's sub-optimal... I would like it to be possible to change some > settings in CMake which would then be output to the generated doxyfile (kind > of like how you can add gcc options, or optional defines, and these will be > passed to the compiler). I'll see if I can get that to work, perhaps after > the holidays. I have attached a CMakeLists.txt that provides a DOXYFILE_EXTRA_FLAGS. Could you check and see if it is what you want? The variable will get applied to both documentation targets (osg and ot). The files also has generation of PACKAGE_ALL which you suggested earlier. I haven't submitted cause I wanted to test it on windows. cheers Mattias > >> Now that I have figured out how to undo a mark_as_advanced maybe I >> should add some mark_as_advanced to the vars that confused you in this >> case. > > Yes, that would be a good idea. It would make the process friendlier. > > Thanks, > > J-S > -- > ______________________________________________________ > Jean-Sebastien Guay [email protected] > http://www.cm-labs.com/ > http://whitestar02.webhop.org/ > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org >
doxyflags.tar.gz
Description: GNU Zip compressed data
_______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
