Build MetaCall with Ruby

[ahmedihabb2]

Description

Build Metacall with Ruby support for MacOS

Type of change

• [x] New feature (non-breaking change which adds functionality)

Checklist:

• [x] I have performed a self-review of my own code.
• [x] I have commented my code, particularly in hard-to-understand areas.
• [ ] I have made corresponding changes to the documentation.
• [x] My changes generate no new warnings.
• [x] I have added tests/screenshots (if any) that prove my fix is effective or that my feature works.
• [x] I have tested the tests implicated (if any) by my own code and they pass (make test or ctest -VV -R <test-name>).
• [x] If my change is significant or breaking, I have passed all tests with ./docker-compose.sh test &> output and attached the

Note:

The following tests FAILED: 22 - metacall-duplicated-symbols-test (Timeout) 25 - metacall-distributable-test (Timeout) 57 - metacall-ruby-parser-integration-test (Timeout)

Check full logs 7_Build.txt

Check related issue

[viferga]

@ahmedihabb2 I have solved the issue of the sanitizer and now we should have visibility respect to the errors.

Another thing is, the file "env.txt" has been renamed to "CMakeConfig.txt" (and it should go inside build folder). Try to use the same name for convention.

I am going to set this PR as draft meanwhile you implement it.

Another thing is, here: https://github.com/metacall/core/blob/b9e44608b934e2e33a5989833d8a137fa0163b4a/tools/metacall-environment.ps1#L46

The equivalent in MacOs is called: -DPython3_FIND_FRAMEWORK=NEVER

This will force to find the installation that you passed with Python3_ROOT_DIR, instead of using the one from the system.