Is it possible to provide a action.yml to make it a github action to support build software in termux?

[Freed-Wu]

Is it possible to provide a action.yml to make it a github action to support build package in termux?

Such as:

.github/workflow/main.yml:

jobs:
  build-in-termux:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: termux/termux-docker@v0.0.1
        with:
          platforms: x86_64, aarch64 # all
          run: |
            gcc main.c -o main-{{ platform }}
          output: main-*
      - uses: actions/upload-artifact@v3
        with:
          path: |
            main-*

[twaik]

You are trying to clone termux-docker's repo. This way you do not invoke docker, you are only getting a set of files to build docker environment...

[robertkirkman]

This issue is asking about this specific type of action.yml file, indicated by the "uses:" directive, which would be a second Dockerfile and action.yml implemented as an abstraction on top of the existing Dockerfile and docker_build.yml that would pass in the "run" "Input", which would most likely have to be a single long command within quotes, with all desired commands separated by &&, and it would not be possible to conveniently alternate between commands by root user and commands by system user, because that type of Action is really intended to have single "Inputs" and "Outputs", and it would not have persistent container contents in between multiple run: directives, unlike the container: directive, which does have persistent container contents in between multiple run: directives. uses: directives are mainly intended for single-purpose, self-contained, well-defined tasks, as opposed to container: directives, which can be used for multi-purpose, open-ended, loosely-defined tasks.

@Freed-Wu If you would maybe like to see a working example of an alternative clone->build->upload-artifact workflow using termux-docker within GitHub Actions via the container: directive instead of a container-action action.yml wrapper, please look at my comment in:

• Poor Github Actions support #62