SSE4
SSE4
from https://github.com/conan-io/conan-center-index/pull/9409 ``` [HOOK - conan-center.py] pre_export(): ERROR: [NO TARGET NAME (KB-H040)] CCI uses the name of the package for cmake generator. Use 'cpp_info.names' instead. (https://github.com/conan-io/conan-center-index/blob/master/docs/error_knowledge_base.md#KB-H040) ``` the recommendation to...
should be a simple check to implement. it allows to consume recipes via `PkgConfigDeps`.
closes: #354 we will need to run hooks against current conan-center to understand the scale of the destruction
in the near future (conan 2.0), old CMake generators (`cmake`, `cmake_multi`, `cmake_paths`, etc.) will be removed, as well as `conan_basic_setup`. targets `CONAN_PKG::` won't be provided any longer. also, variables like...
the current format is: ``` 1.75.0: - patch_file: "patches/boost_build_qcc_fix_debug_build_parameter_since_1_74.patch" base_path: "source_subfolder" - patch_file: "patches/python_base_prefix_since_1_74.patch" base_path: "source_subfolder" ``` we want more fields according to the discussion at https://github.com/conan-io/conan-center-index/pull/3951 the proposal format...
right now our conan-centre hook requires CMake 3.1 [here](https://github.com/conan-io/hooks/blob/master/hooks/conan-center.py#L495). it outputs the following message: ``` The test_packages/CMakeLists.txt requires CMake 3.1 at least. Update to 'cmake_minimum_required(VERSION 3.1) ``` while it says...
/cc @uilianries @jgsogo there is some probability, that in the future conan might remove **six** dependency. there are some existing recipes (example https://github.com/conan-io/conan-center-index/pull/1060/files) using **six** (for StringIO, urllib, etc.). we...
from https://github.com/conan-io/conan-center-index/pull/1375/files#r409740469 /cc @uilianries I am very tentative about this, might be super annoying
from https://github.com/conan-io/conan-center-index/pull/1254#discussion_r403488929 /cc @uilianries for `CMakeLists.txt` and `test_package/CMakeLists.txt`, we may advice `set_property` over `set_target_properties` for advanced CMake compatibility
is it somehow possible more or less generic checks for undocumented APIs in recipes? we had some issues with it previously, e.g.: https://github.com/conan-io/conan-center-index/pull/1293#discussion_r408189278 https://github.com/conan-io/conan-center-index/pull/1284 maybe we can avoid such kind...