Try swift

[commjoen]

What kind of changes does this PR include?

• Fixes or refactors
• A new challenge
• Additional documentation
• Something else

Description

This builds out a Swift version of the wrongsecrets binaries.

Relations

References

Checklist:

• All the contributions made are solely the work of me and my co-authors
• I tested the changes in this PR (if applicable)
• I added unit tests to ensure my change works (when change in Java or on front-end code)
• Quickbuild.sh is extended to compile the binary for all target environnments
• Github actions are implemented to publish the new challenge <-- TO FIX FOR MUSL!
• A spoil command is implemented to return the actual answer
• The correct and incorrect answer strings are compliant with Contributing.md.
• The PR passes pre-commit hooks and automated tests

[commjoen]

We are waiting on swiftlang/swift#62245 as we will need Alpine support for our webtop and need freedom for our java base container to be moveable to alpine again.

[commjoen]

Track swiftlang/swift#47209 :)

[commjoen]

Chatgpt sais (TLDR: tested does not work...):
To make Swift run on musl libc instead of glibc, you would typically need to cross-compile Swift with musl support. Here's a general approach to do this:

1. Install musl-libc: First, you need to ensure that musl-libc is installed on your system. If it's not already installed, you can usually find it in your package manager. For example, on Alpine Linux, you can install musl-dev package.

2. Obtain the Swift source code: Clone the Swift source code from the official repository:

   git clone https://github.com/apple/swift.git
   

3. Cross-compile Swift with musl support: You'll need to configure Swift's build system to use musl. This typically involves setting up the appropriate flags to point to musl headers and libraries. You can do this by modifying the build script or using cmake directly. Here's a rough outline of how you might do it:

   cd swift
   mkdir build-musl && cd build-musl
   ../configure --target=x86_64-unknown-linux-musl --build=arm-linux-androideabi --enable-optimized --disable-debuginfo --enable-assertions --sysroot=/path/to/musl/sysroot
   make -j8
   

   Replace /path/to/musl/sysroot with the path to your musl sysroot directory. You may need to adjust other flags depending on your system configuration.

4. Test your musl-enabled Swift build: Once the build process completes successfully, you can test your musl-enabled Swift build by running Swift REPL or compiling and running a simple Swift program.

Keep in mind that cross-compiling software can be complex and may require tweaking depending on your specific setup and requirements. You may encounter issues with dependencies, compiler flags, or compatibility issues between Swift and musl. Be prepared to do some troubleshooting and experimentation to get everything working correctly.

[commjoen]

Static linking also does not work as we need Foundation. (swiftc -emit-executable -static-executable )

[commjoen]

Pending https://stackoverflow.com/questions/78072650/how-can-i-compile-a-simple-swift-cli-program-for-alpine

[commjoen]

filed a bug/request for help at SwiftyLab/setup-swift#369