| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 1 | |
Hello, could anyone give me a short tip how to build the qt documentation form source on windows? doing a qmake, nmake doesn't seem to touch the doc folder, and qtassistant is empty. -- [ signature omitted ]
On Thursday 03 April 2008 13:59:39 Wente, Andreas wrote: > Hello, > > could anyone give me a short tip how to build the qt documentation form > source on windows? doing a qmake, nmake doesn't seem to touch the doc > folder, and qtassistant is empty. nmake docs -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Thiago Macieira schrieb: > On Thursday 03 April 2008 13:59:39 Wente, Andreas wrote: >> Hello, >> >> could anyone give me a short tip how to build the qt documentation form >> source on windows? doing a qmake, nmake doesn't seem to touch the doc >> folder, and qtassistant is empty. > > nmake docs > Looks like this does not work for mingw - is this a known bug? Christian -- [ signature omitted ]
On Thursday 03 April 2008 20:31:28 Christian Ehrlicher wrote: > Thiago Macieira schrieb: > > On Thursday 03 April 2008 13:59:39 Wente, Andreas wrote: > >> Hello, > >> > >> could anyone give me a short tip how to build the qt documentation form > >> source on windows? doing a qmake, nmake doesn't seem to touch the doc > >> folder, and qtassistant is empty. > > > > nmake docs > > Looks like this does not work for mingw - is this a known bug? No, it should work. But I haven't tested in a while. -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Christian Ehrlicher wrote: >> [...] >> nmake docs >> > Looks like this does not work for mingw - is this a known bug? Try it with "mingw32-make docs" :-) If this doesn't work, too : Which version of Qt are you using? And what is the command line output? Kai Koehne -- [ signature omitted ]
> Von: Kai Koehne
> Christian Ehrlicher wrote:
> >> [...]
> >> nmake docs
> >>
> > Looks like this does not work for mingw - is this a known bug?
> Try it with "mingw32-make docs" :-)
>
> If this doesn't work, too : Which version of Qt are you using? And what
> is the command line output?
>
I'm using qt-copy (qt4.4.0-rc1).
It does not work because my .qmake.cache contains unix-style paths (when using msvc mkspec, the paths are converted to windows-style).
This leads to following command generated by doc.pri:
QDOC = cd e:/kde/kde-mingw/qt/tools/qdoc3/test && ...
which is not accepted as a valid path (e:\kde/kde-mingw/qt/tools/qdoc3/test *is* a valid path - don't know why and also don't want to know ... )
For msvc I get the following path which works:
QDOC = cd e:\kde\kde-msvc\qt/tools/qdoc3/test && ...
A quick hack would be to replace all '/' with '\\' in QDOC with replace() macro.
I already sent this to thiago macieira in reply to his thread on k-c-d but he had no time to look into this issue until now.
Christian
--
[ signature omitted ]
Christian Ehrlicher wrote: >> Von: Kai Koehne >> Christian Ehrlicher wrote: >> >>>> [...] >>>> nmake docs >>>> >>>> >>> Looks like this does not work for mingw - is this a known bug? >>> >> Try it with "mingw32-make docs" :-) >> >> If this doesn't work, too : Which version of Qt are you using? And what >> is the command line output? >> >> > I'm using qt-copy (qt4.4.0-rc1). > It does not work because my .qmake.cache contains unix-style paths (when using msvc mkspec, the paths are converted to windows-style). > This leads to following command generated by doc.pri: > QDOC = cd e:/kde/kde-mingw/qt/tools/qdoc3/test && ... > This should work with mingw32-make. > which is not accepted as a valid path (e:\kde/kde-mingw/qt/tools/qdoc3/test *is* a valid path - don't know why and also don't want to know ... ) > > I just downloaded the rc1-package, re-compiled it with mingw and could run "mingw32-make docs" without any problems. Please make sure that you are running a recent version of mingw32-make (I'm using v3.81), and configure/compile qt also with mingw. In general it is a good idea to strictly separate the mingw and msvc environments. Regards Kai Koehne -- [ signature omitted ]
On Friday 04 April 2008 16:32:21 Kai Koehne wrote: > I just downloaded the rc1-package, re-compiled it with mingw and could > run "mingw32-make docs" without any problems. Do that from a snapshot. The RC1 packages come with docs pre-generated. (That's one of the reasons why they're so big) -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Christian Ehrlicher wrote: > I'm using qt-copy (qt4.4.0-rc1). > It does not work because my .qmake.cache contains unix-style paths (when using msvc mkspec, the paths are converted to windows-style). > This leads to following command generated by doc.pri: > QDOC = cd e:/kde/kde-mingw/qt/tools/qdoc3/test && ... > > which is not accepted as a valid path (e:\kde/kde-mingw/qt/tools/qdoc3/test *is* a valid path - don't know why and also don't want to know ... ) > Hi, we were now able to reproduce it. "cd C:/" works for me because I'm using Windows Vista; It fails with XP. The incorrect path seems to be a qmake problem. Thanks for spotting it! I'll look into it next week. Kai Koehne -- [ signature omitted ]
Kai Koehne schrieb: > Christian Ehrlicher wrote: >> I'm using qt-copy (qt4.4.0-rc1). >> It does not work because my .qmake.cache contains unix-style paths >> (when using msvc mkspec, the paths are converted to windows-style). >> This leads to following command generated by doc.pri: >> QDOC = cd e:/kde/kde-mingw/qt/tools/qdoc3/test && ... >> >> which is not accepted as a valid path >> (e:\kde/kde-mingw/qt/tools/qdoc3/test *is* a valid path - don't know >> why and also don't want to know ... ) >> > Hi, > > we were now able to reproduce it. "cd C:/" works for me because I'm > using Windows Vista; It fails with XP. The incorrect path seems to be a > qmake problem. > > Thanks for spotting it! I'll look into it next week. > These are good news - thx for looking into this. Christian -- [ signature omitted ]