MACOS compile with user_code plugin

[Yushan-Wang]

When trying to compile the user-code plugin on macOS, the compiler could not find the header link.h

List of things to check before making a PR

Before merging your code, please check the following:

• you have added a line describing your changes to the Changelog;
• you have added unit tests for any new or improved feature;
• In case you updated dependencies, you have checked pdi/docs/CheckList.md
• you have checked your code format:
  • you have checked that you respect all conventions specified in CONTRIBUTING.md;
  • you have checked that the indentation and formatting conforms to the .clang-format;
  • you have documented with doxygen any new or changed function / class;
• you have correctly updated the copyright headers:
  • your institution is in the copyright header of every file you (substantially) modified;
  • you have checked that the end-year of the copyright there is the current one;
• you have updated the AUTHORS file:
  • you have added yourself to the AUTHORS file;
  • if this is a new contribution, you have added it to the AUTHORS file;
• you have added everything to the user documentation:
  • any new CMake configuration option;
  • any change in the yaml config;
  • any change to the public or plugin API;
  • any other new or changed user-facing feature;
  • any change to the dependencies;
• you have correctly linked your MR to one or more issues:
  • your MR solves an identified issue;
  • your commit contain the Fix #issue keyword to autoclose the issue when merged.

[tpadioleau]

This seems to work fine on macOS, see the CI here https://github.com/tpadioleau/test_macos/actions/runs/13736876284/job/38421624228

[jbigot]

Could we also add an issue about adding a MacOS runner for the tests

[jbigot]

Looks great, thanks!

[benoitmartin88]

Duplicate of #555

[jbigot]

I would recommend to make separate branches that each start from main and handle one issue and then make a branch that merge them all on your side for testing

[Yushan-Wang]

I would recommend to make separate branches that each start from main and handle one issue and then make a branch that merge them all on your side for testing

Sure, I'll do that!