Skip to content
  • 0 Votes
    5 Posts
    429 Views
    A

    @cristian-adam I changed to https://download.qt.io/development_releases/prebuilt/libclang/libclang-release_60-windows-vs2015_64-clazy.7z and it worked! Thank you very much!

  • 0 Votes
    1 Posts
    609 Views
    No one has replied
  • 0 Votes
    5 Posts
    695 Views
    A

    @kkoehne said in QDoc doesn't generate all the documentation.:

    MMh .. sounds indeed that something goes wrong here, then.

    Can you create a somewhat minimal example, and open a bug report at https://bugreports.qt.io/projects/QTBUG, component 'Build tools: qdoc'?

    Sure!
    I'll prepare something. Maybe it's a particular configuration that leads to some kind of problem.

    Thanks a lot in advance.

    I'll keep you posted :-)!

  • 0 Votes
    4 Posts
    532 Views
    T

    Still looking for a solution

  • 0 Votes
    26 Posts
    5k Views
    F

    @mrjj
    Qt 5.12.4 (GCC 9.1.0, 64 bit) installed on MSYS.

  • QHelpEngine

    Unsolved General and Desktop
    6
    0 Votes
    6 Posts
    2k Views
    Gojir4G

    @JonB said in QHelpEngine:

    Or, does the code at https://github.com/srish/QtHelpManual/blob/master/main.cpp (a) work and (b) help you?

    I tried this and it almost works. Almost because only the root link from the index view is working, then I have to use links from the content view to navigate. Links under the root item (children) are not working from the index view and clicking on them add error messages in output:

    QFSFileEngine::open: No file name specified QTextBrowser: No document for qthelp://org.qt-project.examples.simpletextviewer/doc/./openfile.html

    When using my own documentation .qhc file, nothing is displayed. So I definitely didn't catch the logic here. I guess I will stay with Doxygen for documentation.

  • 0 Votes
    2 Posts
    900 Views
    SGaistS

    Hi,

    Can you share the thread where you find that ?

    If you want such a status report, you should rather check the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

  • 0 Votes
    8 Posts
    2k Views
    SGaistS

    The technique was to use a qdoc configuration file and load the appropriate Qt features.

    In the end, the library was converted to a Qt module.

  • 0 Votes
    5 Posts
    2k Views
    C

    @vishnu In a project called RBIMS, I created a text docuemt called RBIMS.qdocconf which contained the following text:

    include(compat.qdocconf) project = RBIMS outputdir += ./html headerdirs += . sourcedirs += . exampledirs = . imagedirs = ./images headers.fileextensions = "*.h *.ch *.h++ *.hh *.hpp *.hxx" sources.fileextensions = "*.cpp *.qdoc *.mm *.qml"

    I used the following command (executed from within my project folder) at the command line:

    ~/Qt/5.15.0/gcc_64/bin/qdoc /home/jim/Qt_Projects/RBIMS/RBIMS.qdocconf

    This produced an XML file in the html folder inside my project.

    <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE QDOCINDEX> <INDEX url="" title="RBIMS Reference Documentation" version="" project="RBIMS"> <namespace name="" status="active" access="public" module="rbims"> ... ... Code removed for brevity ... virtual="non" const="false" static="false" final="false" override="false" type="bool" signature="bool createDatabase()"/> <function name="database" fullname="database::database" href="database.html#database" status="active" access="public" location="database.h" filepath="/home/jim/Qt_Projects/RBIMS/database.h" lineno="36" documented="true" meta="constructor" virtual="non" const="false" static="false" final="false" override="false" type="" brief="Database::database test constructor doc parent" signature="database(int *parent)"> <parameter type="int *" name="parent" default="nullptr"/> </function>

    You can see (toward the end) that ....

    brief="Database::database test constructor doc parent"

    is created, which was a

    /*! * \brief database::database test constructor doc * \param parent */

    Qdoc comment in my code.