. . . . . . . . . . . . . . . . . . . . . . 69 7 Developing packages 75 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . 69 7 Developing packages 75 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . 68 7 Developing packages 75 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 12.5 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 12 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

. . . . . . . . . . . . . . . . . . . . . . 67 7 Developing packages 73 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . 79 7 Developing packages 85 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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)

. . . . . . . . . . . . . . . . . . . . . . 70 7 Developing packages 77 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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

. . . . . . . . . . . . . . . . . . . . . . 75 7 Developing packages 81 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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)

. . . . . . . . . . . . . . . . . . . . . . 71 7 Developing packages 77 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 7.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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)

. . . . . . . . . . . . . . . . . . . . . . 70 7 Developing packages 77 7.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 7.2 Packages in 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

. . . . . . . . . . . . . . . . . . . . . . 87 8 Developing packages 93 8.1 Package development flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 8.2 Packages in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266 14.6 Version Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 14 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)