WIN32 _WINDOWS compile definitions are defined for MinGW
" " are added to shiboken command generator parameters for all lines which contains ${PATH_SEP}
For example:
--include-paths=${pyside_SOURCE_DIR}${PATH_SEP}${QT_INCLUDE_DIR}
When PATH_SEP is ';' the line becomes
--include-paths=${pyside_SOURCE_DIR};${QT_INCLUDE_DIR}
which for cmake is
--include-paths=${pyside_SOURCE_DIR} ${QT_INCLUDE_DIR}
Let PySide build with MinGW
WIN32 _WINDOWS compile definitions are defined for MinGW
" " are added to shiboken command generator parameters for all lines which contains ${PATH_SEP}
For example:
--include-paths=${pyside_SOURCE_DIR}${PATH_SEP}${QT_INCLUDE_DIR}
When PATH_SEP is ';' the line becomes--include-paths=${pyside_SOURCE_DIR};${QT_INCLUDE_DIR}
which for cmake is--include-paths=${pyside_SOURCE_DIR} ${QT_INCLUDE_DIR}
And Shiboken fails to run
Signed-off-by: Viacheslav Yartsev salava@ahead.io