Skip to content

Improve build-system for ease of use #4

@JayFoxRox

Description

@JayFoxRox

The build-system should be refactored. Ideally to CMake (in my opinion), or at least a helper script to do the steps from the README.

The steps are just too annoying for a small utility like this.
In particular, this step: "3. Set URHO3D_HOME and URHOX_HOME variable path in QtCreator"

  • It shouldn't be necessary to manually mix qmake and cmake.
  • The build-system should find system-wide installation of Urho3D, or there should be a helper to install it.
  • Urhox should probably be bundled with Spkgen or CMake should be used to find it, with a helper to download it.

Another option would be to keep the complicated build-system, but provide a webtool. Urho3D already has demos for the web using emscripten. There's also Qt for wasm, so deploying this way might be a good alternative to let people play with SPARK and spkgen.


Lastly, this also partially affects https://github.com/fredakilla/SPARK - I think the changes should be upstreamed, or the library should be made independent for exposure. It's the only easy-to-use version of SPARK that I found (installing system-wide is a critical feature to me).
SPARK seems to be a cool library, but the upstream build-system and lack of documentation probably hurt its usability; the confusing ecosystem (there's still a sourceforge page for it, which looks more "official") and tooling should be improved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions