-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Library building for Windows compilers #1476
base: main
Are you sure you want to change the base?
Conversation
Does not introduce a new LibraryBuilder class in order to reuse as much as possible from existing (proven) code |
msvc builds done, now remains only conan stuff which is probably the hardest |
Am at a a bit of deadlock now. Will write it down in the hopes that I miraculously think of the correct solution. The problem: When building the libraries for Windows, I force the recipe for conan to be a 'package install' which means it packages the install directory and you say to cmake hey install it to that directory. This is done to avoid having headers on disk permanently like we have for most of our Linux libraries. But the consequence of that is that the conan recipe changes, and that's replaced on the conan server for that library version. Now, technically, CE doesn't actually use the recipes. It's only for telling conan what to zip up and upload. But if the recipe is changed, will it also say it needs reuploading for compilers that already have an upload? I need to figure this out first. I think I can check this by uploading a msvc build and then try to upload a build for a gcc that we've already done in the past. But I do need to disable force uploading before I do that. Doing that now before continuing this writeup. |
Ok, so changing the recipe doesn't cause issues with checking if a build has already been done. Next issue: Not having a directory where all the libraries are installed is obviously an issue for our I have tested the process simply by calling So we need a way to temporary install the library version before building it. The question is how, options are:
Either way, it will always cause installation of the library and will slow down the build even if there's nothing to build. I think it might be best to integrate it into the python script, since the Will give that a go. |
Was pretty easy to add |
continuing in #1491 |
Part of #1332
Will need to address the following:
Will not include (things to be added later):