| Supported Platforms | |
If you are not sure whether gec works with your C compiler on your operating system and hardware, you can see below if others already succeeded in doing so. If your platform or C compiler does not appear in this list, you can still give it a try. You just have to follow the instructions given at the end of this chapter.
This table shows the C compilers and platforms on which gec has already been used successfully:
| Operating System | Hardware | C Compiler | Comment |
| Linux Ubuntu 24.04 | x86_64 | gcc 13.3.0 | Using GitHub Actions and Azure DevOps |
| Linux Ubuntu 24.04 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions and Azure DevOps |
| Linux Ubuntu 24.04 | arm64 | gcc 13.3.0 | Using GitHub Actions |
| Linux Ubuntu 24.04 | arm64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions |
| Linux Ubuntu 22.04 | x86_64 | gcc 11.4.0 | Using GitHub Actions and GitLab Pipelines |
| Linux Ubuntu 22.04 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions |
| Linux Ubuntu 22.04 | arm64 | gcc 11.4.0 | Using GitHub Actions and Azure DevOps |
| Linux Ubuntu 22.04 | arm64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions and Azure DevOps |
| MacOS 15.5 | x86_64 | clang 17.0.0 | Using Azure DevOps |
| MacOS 15.5 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using Azure DevOps |
| MacOS 15.5 | arm64 | clang 17.0.0 | Using GitHub Actions |
| MacOS 15.5 | arm64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions |
| MacOS 14.7.6 | x86_64 | clang 15.0.0 | Using Azure DevOps |
| MacOS 14.7.6 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using Azure DevOps |
| MacOS 14.7.6 | arm64 | clang 15.0.0 | Using GitHub Actions |
| MacOS 14.7.6 | arm64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions |
| MacOS 13.7.6 | x86_64 | clang 15.0.0 | Using GitHub Actions and Azure DevOps |
| MacOS 13.7.6 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions Azure DevOps |
| Windows 2025 | x86_64 | msc 17 (Visual Studio 2022) | Using GitHub Actions and Azure DevOps |
| Windows 2025 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions and Azure DevOps |
| Windows 2022 | x86_64 | msc 17 (Visual Studio 2022) | Using GitHub Actions and Azure DevOps |
| Windows 2022 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions, Azure DevOps and GitLab Pipelines |
| Windows 11 | x86_64 | msc 17 (Visual Studio 2022) | On personal computer |
| Windows 11 | x86_64 | zig toolchain 0.15.1 (clang 20.1.2) | On personal computer |
| Windows 11 | arm64 | msc 17 (Visual Studio 2022) | Using GitHub Actions |
| Windows 11 | arm64 | zig toolchain 0.15.1 (clang 20.1.2) | Using GitHub Actions |
This section explains what to do in order to test gec on a new platform or with a new C compiler using the code from the Git repository.
First you need to check-out the code from the Gobo Git repository. Then you should set the environment variable $GOBO to the directory where you checked out the code, and add $GOBO/bin to your $PATH. All this is explained in $GOBO/bin/Readme.md. If you are using a C compiler other than Microsoft Visual C cl on Windows or GNU gcc on other operating systems such as Linux, you should provide a configuration file for your C compiler as explained in the section "Back-end C compiler".
Then, depending on your platform and your C compiler, you should run either one of these commands:
If this completes successfully (no "BUILD FAILED!" message), you can then run the following test:%GOB%\bin\install.bat <c_compiler> $GOBO/bin/install.sh <c_compiler>
cd $GOBO geant test_ge
Please don't forget to send feedbacks to the Gobo development team about your experiments, and whether we should add new entries to the list of platforms and C compilers above or add new config files to $GOBO/tool/gec/backend/c/config/.
|
Copyright © 2006-2025, Eric Bezault mailto:ericb@gobosoft.com https://www.gobosoft.com Last Updated: 2 September 2025 |
  |