iox-#2325 support bzlmod

[wep21]

Notes for Reviewer

Pre-Review Checklist for the PR Author

1. Code follows the coding style of CONTRIBUTING.md
2. Tests follow the best practice for testing
3. Changelog updated in the unreleased section including API breaking changes
4. Branch follows the naming format (iox-123-this-is-a-branch)
5. Commits messages are according to this guideline
   • Commit messages have the issue ID (iox-#123 commit text)
   • Commit author matches Eclipse Contributor Agreement (and ECA is signed)
6. Update the PR title
   • Follow the same conventions as for commit messages
   • Link to the relevant issue
7. Relevant issues are linked
8. Add sensible notes for the reviewer
9. All checks have passed (except task-list-completed)
10. Assign PR to reviewer

Checklist for the PR Reviewer

• Consider a second reviewer for complex new features or larger refactorings
• Commits are properly organized and messages are according to the guideline
• Code according to our coding style and naming conventions
• Unit tests have been written for new behavior
• Public API changes are documented via doxygen
• Copyright owner are updated in the changed files
• All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
• PR title describes the changes

Post-review Checklist for the PR Author

1. All open points are addressed and tracked via issues

References

• Closes Port iceoryx to bzlmod #2325

[elBoberido]

@wep21 wow, this was fast. Thanks very much for taking care of this.

We have still users who are relying on the old WORKSPACE approach so we might need to restore some of the deleted files for the time being.

I'll check whether the users I know of are able to use dependencies which use bzlmod. If this is indeed the case, this can be merged as is (once the CI is green), if not the files from the bazel folder need to be restored.

Anyway, it's is great to move this forward :)

Edit: It seems that there are some issues with //:buildifier_lint_check

[wep21]

@elBoberido

I'll check whether the users I know of are able to use dependencies which use bzlmod. If this is indeed the case, this can be merged as is (once the CI is green), if not the files from the bazel folder need to be restored.

I restored old files once and added WORKSPACE.bzlmod for compatibility.

Edit: It seems that there are some issues with //:buildifier_lint_check

Let me check the error.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.23%. Comparing base (bf4e66a) to head (417eaba).
Report is 36 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2338   +/-   ##
=======================================
  Coverage   78.22%   78.23%           
=======================================
  Files         433      433           
  Lines       16034    16033    -1     
  Branches     2302     2299    -3     
=======================================
  Hits        12543    12543           
- Misses       2644     2647    +3     
+ Partials      847      843    -4     

Flag	Coverage Δ
unittests	78.05% <ø> (+<0.01%)	⬆️
unittests_timing	15.06% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 17 files with indirect coverage changes

[elBoberido]

Just wanted to merge but then I noticed that there is no entry in the changelig.

Can you please add an entry to the feature section of doc/website/release-notes/iceoryx-unreleased.md. The format is the name of the issue which is fixed and the link to the issue.

[wep21]

Can you please add an entry to the feature section of doc/website/release-notes/iceoryx-unreleased.md. The format is the name of the issue which is fixed and the link to the issue.

added at 417eaba

[elBoberido]

@wep21 thanks for your contribution and your patience. If you like to continue with bazel, there is some work on iceoryx2 which we could look at.