Skip to content

Avoid making the user build something if you have the artifacts ready, pretty please? #213

@gabriele2000

Description

@gabriele2000

You have the actions that makes the linux build too, instead you're making users compile something, something that makes CMake complain if someone doesn't have the requirements that you didn't even specify.

After ONE HOUR of pulling each one of my hairs, in the most painful way possible, I go "for the lolz" in "Actions" and find the artifacts FOR LINUX that WORKS TOO.

How about including them when you release something, or at least telling potential users that "artifacts exists too, although we suggest to compile everything from scratch?"
"BTW here's a docker image to build it, so it'll work and the build will be reproducible".

Sincerely, someone who spent more than one hour unsuccesfully compiling stuff because of untold requirements, JUST TO FIND THE LAUNCHER BUILT THOUGH "ACTIONS".

Just for the sake of helping everyone else, I'll set up a docker image and create some kind of automated stuff to build BeamMP-Launcher, no one, NO ONE, should have this pain.
NO ONE.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions