| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
Use the QtDeclarative parser instead of Qt Creator's QML parser.
Split the QML visitor into documentation and markup visitors.
The code marker used for each file is now determined from its extension.
|
| |
|
|
|
|
|
| |
The full range of file types is specified in the configuration file.
Each parser is asked if it handles each file.
The pure documentation parser conceptually handles qdoc files, but it
uses the same code as the C++ parser.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Removed the unused ApiGenerator class.
Removed archive and uncompression support not used in Qt.
Removed the unused WebXML generator used to dump documentation as XML
for an ancient documentation Web project.
|
| |
|
|
|
|
|
|
| |
Many of the generators were unused.
The old QSA and Qt Script parsers were unused.
We no longer use DCF files for Qt Assistant.
We no longer generate Qt Jambi documentation, and qdoc3 was not used
for much of that process, making some of the relevant files obsolete.
|
| |
|
|
|
| |
as a side effect, the target is now named html-docs instead of docs to
be consistent with the qt docs.
|
| | |
|
| |
|
|
|
| |
At the moment, it is just like the HTML
generator, but with a different class name.
|
| |
|
|
| |
Reviewed-by: joerg
|
| |
|
|
|
|
|
| |
This allows building documentation even when cross-compiling. Note
that for official documentation, you should always use your host's
qdoc3 binary. This qmake option is for testing whether you introduced
new qdoc warnings even if you don't have a native build around.
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
| |
needed for building qtmobility and qtcreator docs without magic.
Reviewed-by: Daniel Molkentin
|
| |
|
|
|
|
|
|
|
|
|
| |
Third time lucky. The first attempt broke source package builds,
because $$QT_BUILD_TREE is not set if you just run qmake on qdoc3.pro,
causing the generated Makefile to try to build /bin/qdoc3. The second
attempt caused similar problems if you weren't building qdoc3 at least
three levels below the root directory, plus the generated makefile had
the target "../../bin/qdoc3" instead of "qdoc3".
Reviewed-by: Lincoln Ramsay
|
| |
|
|
|
|
|
|
| |
When mkdist builds qdoc, it uses a shadow build outside Qt's build. So
.qmake.cache is not present. That led qmake to try and write to /bin,
which would obviously fail.
Reviewed-by: TrustMe
|
| |
|
|
|
|
|
| |
Most Linux distributions already move qdoc3 to that place for exactly
this reason anyway.
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
-debug/release/debug_and_release
- build qdoc3 always into tools\qdoc3 rathern than release/debug subdirs
- call it from there
Reviewed-by: Marius SO
|
| | |
|
| |
|
|
|
| |
Reduces the number of qmalloc calls by 9% and reduces the instruction
count as reported by valgrind by 2% in a release build.
|
| | |
|
| |
|
|
|
|
|
| |
By default there is no debug version built of qdoc3.
In this case we should call the release build.
Reviewed-by: kh
|
| |
|
