* update to 5.12.4
* removed port qt5-modularscripts and split it functionality into more functions into qt5-base
* added qt_port_hashes.cmake for simpler upgrade.
* added optional VCPKG_QT_HOST_MKSPEC and VCPKG_QT_TARGET_MKSPEC to select QTs build mkspecs from a triplet
* qt_<config>.conf are now copied from the build dir instead from the port dir
* fixed freetype dependencies.
* cleanup of vcpkg_qmake scripts. No strange/unclear replacements anymore.
* introduced vcpkg_buildpath_length_warning
* changed directory layout of the qt5 installation executables and mkspecs a bit.
* First pass wren port
* Add warnings defs, dont specifically use static
* Revert warnings
* See if bringing back new lines fixes windows build issues
* Try force static
* Remove STATIC
* Force static
* [vcl] add vector class library version 2
* fix target path
* renamed library to vectorclass.
Improved CMakelists.txt.
Added early architecture failure
* don't perform changes in the source dir and make cxx_std_17 a build requirement
* update to tagged version 2.00.01
* update version in CMakeLists.txt
* refactored CMakeLists.txt
* [wampcc] Add new port
* Cleanup
* Allow shared build for non-Windows systems;
Add utils and tools features;
Add messages about broken Windows build;
* Make version based on date
* Drop comment
* [ixwebsocket] update to 5.0.6 to fix Windows problem
Some test started to fail on Windows in the 5.0 branch.
```
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
ERROR: Unable to connect to echo.websocket.org on port 80, error: Connect error: No error
```
We figured it out and fixed it. This issue has more details. https://github.com/machinezone/IXWebSocket/issues/103
* ixwebsocket: update to 6.1.0
