-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use Conan 2 #64
base: main
Are you sure you want to change the base?
Use Conan 2 #64
Conversation
5c05042
to
2d45839
Compare
55b5dc3
to
c0154f7
Compare
d51500c
to
3ec21d8
Compare
c8668c2
to
73c7d4d
Compare
01d4393
to
9fbffa4
Compare
9fbffa4
to
eb79e2e
Compare
Waiting for emsdk linux64 build clarification. |
f2058b3
to
9a9cfbc
Compare
9a9cfbc
to
68f0893
Compare
@Waguramu @josephbirkner, do we have some (new) minimum version requirements on emsdk Node.js durring build? These build errors appeared after rebasing this PR on master. |
Yes, we upgraded to 3.1.56 due to this: emscripten-core/emscripten#21460 |
Ok. Conan has no emsdk > 3.1.50 yet, so we either have to wait or get conan to use the hosts emsdk. I will have a look into the second option later; there is something like |
Use Conan 2 for package management.
Emscripten + Node.js get installed via Conan.
There is currently a problem of Conan packages not allowing to override their tool-requirements, so we installnvm
andnode.js v21
in thebuild-ui.bash
script into a temporary directory to force override the node version Conan installs for us (which is too old for angular). See: conan-io/conan-center-index#23088.This also fixes problems with conflicting CMake targets from cesium by building cesium as an external project (see
cmake/cesium.cmake
).The cross-build is set up using a Conan profile.