Workaround with Github Actions and Concord

[mrtuxa]

name: Concord Compiling

on:
  push:
    [ $default-branch ]
  pull_request:
    branches: [ $default-branch ]
  dispatch:

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v3

      - name: Cloning Concord from Github
        run: git clone https://github.com/Cogmasters/concord.git && cd
      
      - name: Installing dependencies
        run: apt update && apt install -y libcurl4-openssl-dev gcc

      - name: Compiling Concord
        run: make -j$(nproc) && sudo make install
      
      - name: Compiling Project
        run: cd ~ && gcc main.c -pthread -ldiscord -lcurl

[HackerSmacker]

What does this add in relation to our current existent system? The current system will compile everything, multiple ways (with and without parallelism, in an effort to weed out Makefile parallelism regressions that might happen); it also compiles the examples and the experimental voice support extensions.

[mrtuxa]

What does this add in relation to our current existent system? The current system will compile everything, multiple ways (with and without parallelism, in an effort to weed out Makefile parallelism regressions that might happen); it also compiles the examples and the experimental voice support extensions.

i thought if you code a bot yourself, an example would be useful

[HackerSmacker]

Ahh, I see. Well, I don't really know if this would be anything past what's already listed in the readme, as most users are probably going to end up not compiling bots through CI (opting to compile them on their own machine and run them, then and there). Nonetheless, this information should be mentioned in the readme (that being "how to actually compile a bot").