[Interest] Makefile target for mocinclude.tmp using inconsistent slashes

Koehne Kai Kai.Koehne at digia.com
Tue Apr 23 08:52:12 CEST 2013



> -----Original Message-----
> From: interest-bounces+kai.koehne=digia.com at qt-project.org
> [mailto:interest-bounces+kai.koehne=digia.com at qt-project.org] On Behalf
> Of James Cotton
> Sent: Monday, April 22, 2013 8:42 PM
> To: interest at qt-project.org
> Subject: [Interest] Makefile target for mocinclude.tmp using inconsistent
> slashes
> 
> I'm having an issue on windows where the mocinclude.tmp makefile
> command lists the Qt includes like this
> 
>         @echo -IC:/TauLabs/ground/gcs/src/plugins/uavobjects>>
> debug/mocinclude.tmp
>         @echo -IC:/TauLabs/ground/gcs/src/libs/libqxt/src/core>>
> debug/mocinclude.tmp
>         @echo -IC:\TauLabs\tools\Qt5.0.2\5.0.2\mingw47_32\include>>
> debug/mocinclude.tmp
>         @echo -IC:\TauLabs\tools\Qt5.0.2\5.0.2\mingw47_32\include/QtSvg>>
> debug/mocinclude.tmp
> 
> the later two are not mangled by echo to create this in mocinclude.tmp
> 
> -IC:/TauLabs/ground/gcs/src/libs/libqxt/src/core
> -IC:/TauLabs/ground/gcs/src/libs/libqxt/src/core/logengines
> -IC: TauLabstoolsQt5.0.25.0.2mingw47_32include
> -IC: TauLabstoolsQt5.0.25.0.2mingw47_32include/QtSvg
> 
> which obviously dosen't work.  This is using makespec win32-g++ I've
> checked that the INCLUDEPATH passed to moc.prf looks like the former.
> Should moc.prf be taking care of converting the paths to use / or escaping
> the slashes?  Alternatively when using msys should the QT_INCLUDE_PATH
> be forced to use / instead?

I'm shooting in the dark here, but consider that
 - building from cmd.exe not inside msys/sh) is the only really tested setup
   (though patches are of course welcome to also support msys/sh)
 - if you build from cmd.exe, make sure you don't have sh.exe in your PATH

Regards

Kai




More information about the Interest mailing list