add flyci ci

[nihui]

No description provided.

[kgantchev]

Hi @nihui,

Thank you for utilizing FlyCI! We would love to get your feedback and add it to our case studies section. It will highlight your project to our visitors and it will help us grow our community. Are you OK with sharing your feedback and getting ruapu highlighted in our case studies section?

If so, please see the pre-filled form below and provide as much of the missing information and we'll draft a case study that we can add to our website (with your permission). Here is the pre-filled form for the case study:

---

Auto-Filled Information

These fields are pre-filled based on your repository's public data. Please review and update if necessary.

• GitHub Username: nihui
• Organization/Project Name: ruapu
• Repository URL: https://github.com/nihui/ruapu
• Visibility: public
• Detected Languages and Technologies: C, CMake, Fortran, Rust, Java, Erlang

Manual Input Required

Please fill out the following sections to the best of your ability:

Project Overview

• Brief description of the project:
  Ruapu is a single-file library designed to detect CPU ISA features across different platforms. It supports a wide array of CPU ISAs and operating systems, providing developers with a tool to optimize their applications based on available hardware capabilities.

Usage of FlyCI MacOS GitHub Action Runners

• What motivated you to use our MacOS runners specifically?

• Can you share any configuration snippets or workflow examples?
  https://github.com/nihui/ruapu/pull/80/files#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03f

  macos-flyci:
    runs-on: flyci-macos-14-xlarge-m2
    steps:
    - uses: actions/checkout@v4
    - name: build-test
      run: |
        clang main.c -o ruapu
        ./ruapu

Benefits and Impact

• What improvements have you noticed since integrating FlyCI's MacOS runners?
  (e.g., performance enhancements, reduced build times, developer productivity, cost savings)

Challenges and Solutions (Optional)

• Have you encountered any challenges with the MacOS runners? How did you overcome them?

• Suggestions for improvements or enhancements for the MacOS runners:

Additional Insights (Optional)

• Any best practices or recommendations for others using MacOS runners?

• Additional comments or experiences you’d like to share:

Consent for Sharing

• I consent to my case study being shared publicly (e.g., in blog posts, documentation, reports).
  • Name/Username to be credited: (optional)

Your feedback is invaluable in helping us improve our MacOS GitHub Action runners and support our community effectively. Thank you for your contribution!