Upgrade base OS and tooling

[Danielius1922]

No description provided.

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)

• .github/workflows/cmake-windows.yml is excluded by !**/*.yml

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes primarily involve formatting and modernization across build scripts, Dockerfiles, macros, and test files. Compiler and coverage tool versioning is updated, especially for Clang, GCC, and gcov tools, with corresponding CMake and shell script adjustments. Several macros and array initializations are reformatted for conciseness. Dockerfiles are updated to use Ubuntu 24.04 and newer Clang versions. Minor code formatting and include adjustments are made in source and test files.

Changes

File(s)	Change Summary
CMakeLists.txt, tools/clang-format.cmake, tools/collect-coverage.sh	Refactored coverage flag handling in CMake; updated clang-format version to 19; improved version-specific gcov/llvm-cov detection in coverage script.
api/cloud/oc_cloud_resource_internal.h, port/oc_loop_event_internal.h, port/zephyr/src/storage.c	Reformatted macro initializations to single-line brace lists for clarity; no logic change.
api/cloud/oc_cloud_schedule.c, api/oc_rep_encode_cbor_internal.h	Reformatted array and macro initializations for readability; no logic or value changes.
api/unittest/coreresourcetest.cpp, api/unittest/resourcetest.cpp	Adjusted indentation of device descriptor initializations in test setup methods.
api/unittest/discovery/discovery.cpp	Added #include <algorithm> for standard algorithm support.
apps/cloud_proxy.c, port/android/ipadapter.c, port/linux/ipadapter.c	Minor formatting adjustments (whitespace, comment alignment) with no logic changes.
docker/apps/Dockerfile.cloud-server-debug, docker/apps/Dockerfile.cloud-server-debug-clang, docker/apps/Dockerfile.dps-cloud-server, docker/apps/Dockerfile.dps-cloud-server-debug	Upgraded base image to Ubuntu 24.04; updated Clang from 15 to 18; added libclang-rt-18-dev and related comments; cleaned up package installation and alternatives.
swig/Makefile, swig/java_lang/build-iotivity-lite.sh	Updated Java compilation flags from 1.7 to 1.8 for source and target compatibility.
swig/swig_interfaces/oc_enums.i	Changed SWIG %rename directive to use %$isenumitem for enum renaming.
tools/pre-commit	Fixed regex patterns by escaping backslashes in byte-string expressions.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant BuildSystem (CMake)
    participant Compiler (GCC/Clang)
    participant CoverageTool (gcov/llvm-cov)
    participant Docker
    participant TestRunner

    User->>BuildSystem: Configure build (with coverage)
    BuildSystem->>Compiler: Set coverage flags (version-specific)
    Compiler-->>BuildSystem: Compile with proper flags
    User->>Docker: Build Docker image
    Docker->>BuildSystem: Use Ubuntu 24.04, Clang 18, etc.
    User->>CoverageTool: Run coverage script
    CoverageTool->>Compiler: Detect version
    CoverageTool->>CoverageTool: Use version-specific gcov/llvm-cov
    User->>TestRunner: Run tests (with updated macros, includes, formatting)
    TestRunner-->>User: Report results

Loading

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ocf-conformance-test-tool]

🎉 Thank you for your code contribution! To guarantee the change/addition is conformant to the OCF Specification, we would like to ask you to execute OCF Conformance Testing of your change ☝️ when your work is ready to be reviewed.

---

ℹ️ To verify your latest change (5168007), label this PR with OCF Conformance Testing.

⚠️ Label is removed with every code change.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud