skip libatomic if mac

[gftabor]

Description

skip libatomic if mac

This check is not correctly stopping -latomic from being used on all apple computers. This causes all downstream libraries to fail to link.

Fixes # (issue)
RoboStack/ros-jazzy#217

Is this user-facing behavior change?

Building

Did you use Generative AI?

No

Additional Information

[gftabor]

I'd love this back ported into jazzy as well.

[fujitatomoya]

@Mergifyio backport lyrical kilted jazzy

[mergify]

backport lyrical kilted jazzy

✅ Backports have been created

Details

• #566 skip libatomic if mac (backport #565) has been created for branch lyrical
• #567 skip libatomic if mac (backport #565) has been created for branch kilted but encountered conflicts

Cherry-pick of 45756eb has failed:

On branch mergify/bp/kilted/pr-565
Your branch is up to date with 'origin/kilted'.

You are currently cherry-picking commit 45756eb.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CMakeLists.txt

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

• #568 skip libatomic if mac (backport #565) has been created for branch jazzy but encountered conflicts

Cherry-pick of 45756eb has failed:

On branch mergify/bp/jazzy/pr-565
Your branch is up to date with 'origin/jazzy'.

You are currently cherry-picking commit 45756eb.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CMakeLists.txt

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally