Add the output_exe option

README.md

@@ -7,6 +7,10 @@ An experimental GitHub Action that compiles a Ring project.
 ### `file` (required)
 - **Description**: The path to the Ring file to build.
 
+### `output_exe` (optional)
+- **Description**: This can be set to 'true' to use Ring2EXE *(to output an executable file)*.
+- **Default**: `false`
+
 ### `args` (optional)
 - **Description**: Additional arguments to pass to Ring2EXE.
 
@@ -22,7 +26,7 @@ An experimental GitHub Action that compiles a Ring project.
 Here’s an example of how to use this action in your workflow:
 
 ```yaml
-uses: ysdragon/ring-action@v1.0.0
+uses: ysdragon/ring-action@v1.0.1
 with:
   file: "program.ring"
 ```

action.yml

@@ -5,6 +5,10 @@ inputs:
   file:
     description: 'The Ring file to compile.'
     required: true
+  output_exe:
+    description: 'This can be set to true to use Ring2EXE (to output an executable file).'
+    required: false
+    default: 'false'
   args:
     description: 'Optional command line flags for the Ring compiler. Use "-static" for static builds for example.'
     required: false

entrypoint.sh

@@ -36,7 +36,7 @@ if [ "$INPUT_VERSION" != "v1.21.2" ]; then
     popd
 fi
 
-# Check if the INPUT_RING_PACKAGE is not empty
+# Check if the INPUT_RING_PACKAGES is not empty
 if [ "$INPUT_RING_PACKAGES" != "" ]; then
     # Split the input string into an array of packages
     IFS=' ' read -r -a packages <<< "$INPUT_RING_PACKAGES"
@@ -47,5 +47,11 @@ if [ "$INPUT_RING_PACKAGES" != "" ]; then
     done
 fi
 
-# Execute ring2exe with the provided arguments and input file
-ring2exe $INPUT_ARGS $INPUT_FILE
+# Check if the INPUT_OUTPUT_EXE is 'true'
+if [ "$INPUT_OUTPUT_EXE" = "true" ]; then
+    # Execute ring2exe with the provided arguments and input file
+    ring2exe $INPUT_ARGS $INPUT_FILE
+else
+    # Execute ring with the provided arguments and input file
+    ring $INPUT_ARGS $INPUT_FILE
+fi