Why doxygen doesn't generate doc for many modules ?
Given the default Doxygen.conf file in docs/ directory, I found that many of the optional modules (even enabled in modules.conf, which of course, I don't expect doxygen to parse/understand), are not included in the documentation. Is it because they are seen as not having any API exposed ? I don't see an explicit list of directories to scan either. What am I missing ? J
Answering my own question... the reason is this line in Doxygen.conf file! EXCLUDE = ../src/mod Of course, I can comment it out and rerun, but wondering, why do we exclude modules from documentation ?? On Sun, Sep 1, 2013 at 10:07 AM, Jayanth Acharya <jayachar88@gmail.com>wrote:
Given the default Doxygen.conf file in docs/ directory, I found that many of the optional modules (even enabled in modules.conf, which of course, I don't expect doxygen to parse/understand), are not included in the documentation. Is it because they are seen as not having any API exposed ? I don't see an explicit list of directories to scan either. What am I missing ?
J
D-uh moment, and apologies for the chatter... Just realized that we also have this -- EXAMPLE_PATH = ../conf ../src/mod So, what does having ../src/mod in examples do ? Why so ? On Mon, Sep 2, 2013 at 12:16 AM, Jayanth Acharya <jayachar88@gmail.com>wrote:
Answering my own question... the reason is this line in Doxygen.conf file!
EXCLUDE = ../src/mod
Of course, I can comment it out and rerun, but wondering, why do we exclude modules from documentation ??
On Sun, Sep 1, 2013 at 10:07 AM, Jayanth Acharya <jayachar88@gmail.com>wrote:
Given the default Doxygen.conf file in docs/ directory, I found that many of the optional modules (even enabled in modules.conf, which of course, I don't expect doxygen to parse/understand), are not included in the documentation. Is it because they are seen as not having any API exposed ? I don't see an explicit list of directories to scan either. What am I missing ?
J
participants (1)
-
Jayanth Acharya