Add CMakePresets.json

Introduce CMakePresests.json which is a simple way to perform incremental build using cmake

New configure resets were added:

• default: Configure compilation with default options
• tests: Same as above but ENABLE_TESTS and SANITIZE_ADDRESS is ON

New build presets were added:

• 5gdefault: Build the software for NR rfsimulator test
• default: same as 5gdefault
• 4gdefault: Build the software for LTE rfsimulator test
• tests: build all unit tests

To configure using configuration preset:

cmake --preset <preset_name>

To build using a build preset:

cmake --build --preset <preset_name>

added documentation label

OAI RAN-Container-Parent build (10499): passed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/10499/)

can you please explain why this would be something we should use?

can you please mention this in doc/BUILD.md?

removed review request for @francescomani

added 1 commit

• 1f7114c4 - Add CMakePresets.json

Compare with previous version

OAI RAN-Container-Parent build (10512): passed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/10512/)

requested review from @schmidtr

changed milestone to %REVIEW_IN_PROGRESS

resolved all threads

requested changes

added 1 commit

• 038270c4 - Add CMakePresets.json

Compare with previous version

OAI RAN-Container-Parent build (10520): passed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/10520/)

changed milestone to %REVIEW_COMPLETED_AND_APPROVED

so I tested a user-preset, and I tried to override the 5g preset to build elsewhere. This is what I came up with, let me know if something is missing or incomplete:

{
    "version": 3,
    "configurePresets": [
        {
            "name": "my5gdefault",
            "inherits": "default",
            "binaryDir": "${sourceDir}/build"
        }
    ],
    "buildPresets": [
        {
            "name": "my5gdefault",
            "configurePreset": "my5gdefault",
            "inherits": "5gdefault"
        }
    ]
}

very nice, works. We can later use that for build_oai, and potentially replace the CI build_oai invocations with presets

added 1 commit

• b69b4dc0 - Add CMakePresets.json

Compare with previous version

OAI RAN-Container-Parent build (10534): passed (https://jenkins-oai.eurecom.fr/job/RAN-Container-Parent/10534/)

resolved all threads

approved this merge request

changed milestone to %OK_TO_BE_MERGED

changed the description

changed milestone to %REVIEW_COMPLETED_AND_APPROVED

Final question, but on the cmake usage. I tried to do both configure&build steps in one, but just giving e.g., the build command line does not work (because that's a superset of the command line options of configure&build). I checked, and there are workflows. Would this be necessary to run both configure&build?

resolved all threads

changed milestone to %OK_TO_BE_MERGED

mentioned in merge request !3032 (merged)

mentioned in commit 65d8d410

merged with merge request !3032 (merged)