[Development] Correct way to create Qt5's doc when packaging from submodules sources.

Lisandro Damián Nicanor Pérez Meyer perezmeyer at gmail.com
Wed Jun 5 15:16:13 CEST 2013

On Wednesday 05 June 2013 11:02:30 Oswald Buddenhagen wrote:
> On Tue, Jun 04, 2013 at 03:13:22PM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
> > We are compiling everything from the submodules tarballs, as it makes
> > maintainance much easier.
> i have bad news for you ...
> the full qt doc generation is a two-pass process which only works with
> the aggregate source tree. otherwise forward references don't work.
> in principle it should be possible to do the reference validation only
> after everything has been built, but that's not how qdoc & co. currently
> work, and it would be a bit annoying for the doc writers, so the system
> would need to support both early and delayed link validation.
> also, automatic generation of cross-module class hierarchy diagrams
> would become *really* challenging, if we ever tried it ...

Thank you both for the answers. We will see what we can do then :-)

Q. How did the programmer die in the shower?
A. He read the shampoo bottle instructions: Lather. Rinse. Repeat.

Lisandro Damián Nicanor Pérez Meyer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130605/9d97be29/attachment.sig>

More information about the Development mailing list