aboutsummaryrefslogtreecommitdiffstats
path: root/PySide2/QtHelp
Commit message (Collapse)AuthorAgeFilesLines
* Remove fixup_headers after fixing shiboken for C++11Christian Tismer2017-05-092-79/+0
| | | | | | | | | | | | The hack for VS 2015 is replaced by a shiboken patch. This must be immediately applied after shiboken was fixed. Reason: The build would work, but Windows will not load because of missing symbols! Task-number: PYSIDE-504 Change-Id: I3ce8989632748b8967228a9993b11c599a858b91 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@qt.io>
* Wrap licenses of the XML[.in] files in C++ commentsFriedemann Kleint2016-10-191-34/+38
| | | | | | | | | The license checker is currently unable to handle XML files; it matches C++ comments. Task-number: PYSIDE-431 Change-Id: Ife6020f2fa666e2fc86e795b4b73f2e05ffed1b3 Reviewed-by: Christian Tismer <tismer@stackless.com>
* Updated remaining license headers of the runtime partsFriedemann Kleint2016-09-291-19/+38
| | | | | Change-Id: Idda6d64540a72095945a94b14efc769e897ef58e Reviewed-by: Lars Knoll <lars.knoll@qt.io>
* Updated license headers of the typesystem XML filesFriedemann Kleint2016-09-271-14/+31
| | | | | Change-Id: Icc28e8b45d9327dc0786e006ab9d414fc24668ee Reviewed-by: Lars Knoll <lars.knoll@qt.io>
* Fix compilation problem with VS2015Christian Tismer2016-06-012-0/+60
| | | | | | | | | | | | | | | | | | | | | | | | VS2015 does not build pyside, because the compiler does not allow access to a private constructor. Older versions of Visual Studio were more sloppy and had no problem. On other platforms, the so-called "protected hack" does the trick. Unfortunately, VS2015 cannot use this hack, because even if enforced, the linker would not find the symbols, because of extensive name mangling. One unpopular solution would be to build Qt5 with the same settings. My current solution is to modify the generated header files by adding public constructors. This is a temporary solution until we improve shiboken or even replace it. [ChangeLog][pyside2][PYSIDE-321] Fix Windows: Pyside2 does not compile with MSVC2015/Update2 Change-Id: I1e278889be688a00b4dd93abd8c87db1a026f006 Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com> Reviewed-by: Christian Tismer <tismer@stackless.com>
* finally, pyside needs to be renamed in the XML filesChristian Tismer2015-09-221-1/+1
| | | | | The XML names like "PySide.QtCore" go into the binaries for import, so it is necessary to change them all. There are also hundreds of Python files which must bechanged, as well.
* not-so-small fix to the huge change.Christian Tismer2015-09-211-1/+1
| | | | | | I just understood what is needed to define a package: The files PySide2Config(...).cmake are crucial, the project names have little to do with that.
* huge change on project layout.Christian Tismer2015-09-212-0/+95
The intention is to have PySide2 and Shiboken2 as project names, to allow for co-existence of PySide and PySide2. This is the first version that builds with these settings on OS X: $ python3 setup.py build --debug --no-examples --ignore-git --qmake=/usr/local/Cellar/qt5/5.5.0/bin/qmake --jobs=9 This is not yet tested.