-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doxygen? #11
Comments
Personally, I don't like Doxy tagging; it's the sort of thing that doubles the edit work when changing The result is that the tags are always less well maintained than the code, so out of date or missing I think that an API definition document is smart, something in latex that is written in the style of the |
I'm strongly in favour of this. The QDP++ manual is an invaluable introduction to the overall structure and design of the package, which is something that is impossible to gain by simply reading the code, and hence essential to newcomers. |
A good manual is really important for the final user that want to start learning the code. No doubt, and we should definitely write. |
I rebump this since documentation is becoming necessary. |
Just wondering about this issue considering an soonish 0.6 release. Is Doxygen generation working, is there anything to do here? |
we have to make sure doxygen is optional, since not every system will have doxygen |
agree on it being optional with a flag. Doxygen generation has not been tested but it should work as most of the code is just c++. |
I can take care of that. |
Hi Guido, |
Ok, let me check. Not immediately as I'm concentrating on the hirep stuff, but in time for the 0.6 release. |
Hi Guido could you please check that the new build options for Doxygen are good for you in |
Few things that are not clear (compiling with clang, I have dot and doxygen in my path) How to compile to get just the html? --enable-doxygen does not seem to work and the configure --help does not say much. I tried --enable-doxygen-dot and --enable-doxygen-pdf too and in both cases it complains with an error like this in the config.log |
Have you tried |
ok thanks, looks working. I think you can move to the develop at this stage anyway. |
Hi Guido I missed that for 0.6, I will merge it with |
This reverts commit 1ba4293.
…d nsp"" This reverts commit 3af4929.
What is the point of view of the developers on starting to write the doxygen annotations before the code becomes too big?
Any other suggestion about the documentation?
The text was updated successfully, but these errors were encountered: