You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
using cmake/hirlam to compile IAL binaries require rearranging of cmake/hirlam, for now too bound to teh HarmonieCSC structure
we could have a separate usecase of Davai, starting from a HarmonieCSC git ref, then running with it a subset of tasks. However this requires the user to have access to Hirlam repositories. And the cmake/hirlam generated binaries require specific environments to be ran (otherwise some linked libraries are missing), which for now prevents from running Davai tests with them.
The text was updated successfully, but these errors were encountered:
The issue is indeed the tight binding between Hirlam scripts and the cmake. We could hack something together but it is not so clear what we achieve and what we are even testing in that case. The solution will also be only working for members of the hirlam github because of the need for our Auxlibs repo. Best would be that we first make the compilation in HarmonieCSC a bit more portable (e.g. treat the Auxlibs as normal external project like we do for field_api etc. Our use of git submodules to handle these dependencies is bad for portability. Then I think we would also need to treat IAL itself as an external project in cmake. So for now I think the easiest solution would be to make sure that our Harmonie MASTERODB becomes portable, i.e. doesn't rely on LD_LIBRRARY_PATH so we can replace the gmkpack MASTERODB from Davai with our MASTERODB in the Davai runs to test the cmake builds
Introduction of an additional "flavour" of compilation, being with cmake/hirlam instead of gmkpack.
Facing some issues during Davai WW3:
-u
) start from an HarmonieCSC git refConclusion of the Davai WW3:
The text was updated successfully, but these errors were encountered: