īTW, #19151 can probably be closed now (see eb1242c).
#Cmake set default code#
A few years ago I wrote some CMake code to set a default if one was not specified, and also populate a list of available options so that it would show up in cmake-gui as a drop down. To conclude: Please confirm that I really should I push the version where setting wxBUILD_COMPATIBILITY to 3.2 sets ON not only WXWIN_COMPATIBILITY_3_2 but also WXWIN_COMPATIBILITY_3_0. CMake has several default build types, but if nothing is specified when configuring your project it defaults to an empty string and no optimization flags are used.
When set to ON, the default, some unittests will be cut short. the API life cycle is: supported -> supported, but deprecated, but still enabled by default -> still supported, but not enabled by default any longer -> not supported, where each arrow corresponds to a minor version change.īut this supports my " WXWIN_COMPATIBILITY_3_0 comment is wrong" argument as the 3.0-compatible APIs (i.e., "still supported, but not enabled by default any longer") should be removed in 3.4 and not 3.6? Either way, the incorrect default value in the comment aside, IMO it would not make sense to have the same comment including the version indicated for API removal for both WXWIN_COMPATIBILITY_3_0 and WXWIN_COMPATIBILITY_3_2. CMake generates a build system from the information given in the CMakeLists. You can try to append paths to CMAKEPREFIXPATH in your project CMakeLists. default interval option of set weeks from the current date configured in main.
Also, we really remove the deprecated functionality in the version after the one in which it was deprecated, i.e. Optionally builds a CMake project using the cmake -build command.
0 kommentar(er)
