| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
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
|
| |
|
