You can also use check_md5(), check_sha1() and check_sha256() from the tools module to
The build() method and define your package() and package_info() accordingly. You already have, even if you don’t have the source code. You can even create packages for pre-compiled libraries
#CMAKE INCLUDE DIRECTORIES RECURSIVE CODE#
The download, unzip utilities can be imported from conan, but you can also use your own code here
#CMAKE INCLUDE DIRECTORIES RECURSIVE DOWNLOAD#
Is a snippet of the conanfile of the Poco library:įrom conans import ConanFile from conans.tools import download, unzip, check_md5, check_sha1, check_sha256 import os import shutil class PocoConan ( ConanFile ): name = "poco" version = "1.6.0" def source ( self ): zip_name = "poco-1.6.0-release.zip" download ( "", zip_name ) # check_md5(zip_name, "51e11f2c02a36689d6ed655b6fff9ec9") # check_sha1(zip_name, "8d87812ce591ced8ce3a022beec1df1c8b2fac87") # check_sha256(zip_name, "653f983c30974d292de58444626884bee84a2731989ff5a336b93a0fef168d79") unzip ( zip_name ) shutil. For that purpose, we have provided some helpers, but you can use your own code or origin as well. You can also useĪnother VCS or direct download/unzip. This will work, as long as git is in your current path (so in Win you probably want to run things in msysgit, cmder, etc). Self.source_folder and the current working directory will be the composition of the base folder (typically where the recipe is) Note, however, that this folderĬan be different if the recipe defines the layout() method and specifies a = "src". The current working directory where the source() method runs is the self.source_folder. run ( "git clone " ) # You can also change branch, commit or whatever # n("cd hello & git checkout 2fe5.") # Or using the Git class: # git = tools.Git(folder="hello") # git.clone("") (Again, this component only has one source dir but you can put a list of multiple source directory paths here and it will work.From conans import ConanFile class HelloConan ( ConanFile ): name = "hello" version = "0.1" settings = "os", "compiler", "build_type", "arch" def source ( self ): self. We do this for our internal unit test components: CMake will use globbing to find all the source files. This can be confusing if you share the codebase with multiple people.ĭespite all this, it is still possible to give a list SRC_DIRS instead of SRCS - similar to the GNU Make build system. The reason for encouraging "source files not directories" is that CMake only re-runs when it is necessary, and if you add a new file to the build when using globbing then CMake will not automatically re-run - CMake needs to be run manually then, or "idf.py reconfigure" needs to be run. If you're updating, you only need one CMakeLists.txt file in each place that you had a component.mk file in the old build system.
(Note this uses a CMake variable called "srcs", this is optional you can also just list all of the source file relative paths one by one after SRCS.
In ESP-IDF build system, this means passing them in by the "SRCS" parameter of idf_component_register. They can all be given in a single CMakeLists.txt file, even when the files are in multiple subdirectories, but CMake recommends listing each file name individually and not using "globbing" techniques like "*". The "recommended CMake Way" is to list all of the source files by name.
0 kommentar(er)
