. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 13.5 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 13 The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 13.5 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 13 The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 13.5 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 13 The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 13.5 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 13 The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple

The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folder that will not exist in another machine. Also, it is very important cmake files were generated there. The build folder is temporary, you should exclude it from version control, so those temporary files are excluded too. Out-of-source builds are also supported. Let’s make and in your path. They are not required by conan, you could use your own build system and version control instead. 6.1.1 Creating the package recipe First, let’s create a folder for our package recipe

The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple and in your path. They are not required by conan, you could use your own build system and version control instead. 5.1.1 Creating the package recipe First, let’s create a folder for our package recipe

The generated files are usually temporary, created in build folders and not committed to version control, as they have paths to local folders that will not exist in another machine. Moreover, it is very generated there too. Note that the build folder is temporary, so you should exclude it from version control to exclude these temporary files. Out-of-source builds are also supported. Let’s look at a simple and in your path. They are not required by conan, you could use your own build system and version control instead. 5.1.1 Creating the Package Recipe First, let’s create a folder for our package recipe

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 13.6 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253 13 Community Edition (CE) is the recommended Conan server to host your own packages privately under your control. Conan is mature and stable, with a strong commitment to forward compatibility (non-breaking policy) Community Edition (CE) is the recommended Conan server to host your own packages pri- vately under your control. It is a free community edition of JFrog Artifactory for Conan packages, including a WebUI, multiple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 13.6 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257 13 Community Edition (CE) is the recommended Conan server to host your own packages privately under your control. Conan is mature and stable, with a strong commitment to forward compatibility (non-breaking policy) Community Edition (CE) is the recommended Conan server to host your own packages pri- vately under your control. It is a free community edition of JFrog Artifactory for Conan packages, including a WebUI, multiple

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 13.6 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 13 Community Edition (CE) is the recommended Conan server to host your own packages privately under your control. Conan is mature and stable, with a strong commitment to forward compatibility (non-breaking policy) Community Edition (CE) is the recommended Conan server to host your own packages pri- vately under your control. It is a free community edition of JFrog Artifactory for Conan packages, including a WebUI, multiple