Closed daljit46 closed 2 weeks ago
clang-tidy review says "All clean, LGTM! :+1:"
clang-tidy review says "All clean, LGTM! :+1:"
Regarding the name, it probably needs to be clear that it's not the entire build that's static, only that outside of core, especially given earlier builds have had full static build capability (though from memory it's been a little patchy at times).
Unfortunately, I don't have good ideas for the name (neither does ChatGPT). The best I could come up with is MRTRIX_BUILD_NON_CORE_STATIC
.
If ChatGPT can't even come up with variable names, is it even fit for purpose? I mean, that's 98% of the work to be done. 🤡 No clear superior alternative to MRTRIX_BUILD_NON_CORE_STATIC
from me. Will take the slight clumsiness for the sake of accuracy.
clang-tidy review says "All clean, LGTM! :+1:"
clang-tidy review says "All clean, LGTM! :+1:"
@Lestropie can we merge this?
As mentioned in the meeting today, it'd make sense for production builds to have the C++ code in
src
built as a static library. This PR adds a newMRTRIX_BUILD_STATIC
option to allow for this (@MRtrix3/mrtrix3-devs if anyone has a better name please let me know). The option is disabled by default and is only intended to be enabled in production and external projects. For every day builds, making shared libraries provides a faster incremental build workflow.