Why didn’t we do so? Well, we have been already working with other package managers before - APT/deb, NuGet, npm and others that our users were requesting - and these packages are mostly just archives with certain meta-information, and that is how we were looking at Conan too, not expecting it to also be able to manage building. So yeah, perhaps if we chose to integrate Conan into our buildsystem and build dependencies from sources, the result would be better ( faster). So we were not making source packages and were not implementing the build() method in recipes.Įffectively, we were prebuilding all our dependencies for all the platforms that we target, and that turned out to be very ( very) time-consuming, so we pretty much didn’t progress beyond that small subset of dependencies from the pilot project created during research. At the first glance it seemed that integrating Conan as a part of our build system would be too disruptive, so we decided to just pack pre-built artifacts from the install destination with export-pkg -pf. I think, this is because we chose a wrong approach to it. jpeg-turbo doesn’t support building with more than one architecture. ![]() Merging different architectures into one universal binary. ![]() ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |