Running configure specifically for apidox

Stephan Kulow coolo at kde.org
Tue Apr 26 09:22:58 BST 2005


Am Dienstag 26 April 2005 10:09 schrieb David Faure:
> On Tuesday 26 April 2005 09:21, Stephan Kulow wrote:
> > Am Montag 25 April 2005 23:08 schrieb Adriaan de Groot:
> > > Is this OK to commit? Renaming is fine by me, I'd probably go with 
> > No, it's not. We use other tricks to make apidox work on ktown at all - 
> > zeroing out DO_NOT_COMPILE is just one more hack to apply without
> > having to polute --help. Because without these hacks, you won't come
> > as far without having a qt-devel installed as ktown.
> 
> But that's the point: instead of applying unstable hack over hack on ktown itself,
> [and basically preventing anyone else from making apidox on their server; keep in
> mind that ktown isn't the only webserver generating apidoxes, e.g. there's koffice.org etc.]
> why not start doing things clean?
> Adriaan's patch is only a beginning, IMHO --enable-apidox (can't we hide it, maybe?)
> could do all the necessary 'hacks' for apidox to run on servers.
Because I don't want to polute our configure checks. 

Greetings, Stephan




More information about the kde-core-devel mailing list