Add Ninja to the list of required tools #2498
Conversation
tronical
added
a:documentation
We have plenty of command lines that explicitly use `-GNinja`, so let's make Ninja a tool that is required. That's easier than changing all the command lines to have two variants (use XX or YY if you have Ninja installed), and we know that the dependency handling works best with Ninja. Fixes #2495
tronical
force-pushed
the
simon/docs-ninja
branch
from
324d2e7 to
f709e33
Compare
There was a problem hiding this comment.
I would still like to keep it as optional.
And btw, there is a bunch of other dependencies that are needed, especially on Linux like all the X11 dev libs.
I think we need a central requirements page for building from source that can be linked from the other ones (currently it is in building.md but it should be separate)
What do you think?
| @@ -3,7 +3,7 @@ | |||
| In this tutorial, we use C++ as the host programming language. We also support other programming languages like | |||
| [Rust](https://slint-ui.com/docs/rust/slint/) or [JavaScript](https://slint-ui.com/docs/node/). | |||
|
|
|||
| You will need a development environment that can compile C++20 with CMake 3.21. | |||
| You will need a development environment that can compile C++20, [CMake 3.21](https://cmake.org/download/), and [Ninja](https://ninja-build.org). | |||
| We don't provide binaries of Slint yet, so we will use the CMake integration that will automatically build | |||
There was a problem hiding this comment.
We now do provide binaries, and it might be easier and faster for newbies to install our binaries than installing rust and compile slint from source.
There was a problem hiding this comment.
We have binaries for Linux and Windows, but not for macOS. We could invest the time to make the macOS binaries work and then change the tutorials to use Slint binary packages. That's what you meant, right?
I suggest to create an issue to track that. I'd think it's best-case 1-2 days of work, worst case 2-3 weeks (macOS binaries may need signing, which may require acquiring a certificate, and we have to build binaries for Apple Silicon as well as x86-64 - ideally combined, but more likely two separate packages to start with).
There was a problem hiding this comment.
This tutorial is not only for macos. We could recommand Windows and Linux user to use our binaries.
There was a problem hiding this comment.
Ah, so you mean to document it like this: If you're on Linux and Windows, use our binaries, if you're on macOS build from source?
In any case, no objections from my side. I think time spent on polishing the C++ tutorial is time well spent.
Co-authored-by: Olivier Goffart <olivier.goffart@slint-ui.com>
Co-authored-by: Olivier Goffart <olivier.goffart@slint-ui.com>
ogoffart
removed
the
candidate-for-bugfix-release
We have plenty of command lines that explicitly use
-GNinja, so let's make Ninja a tool that is required. That's easier than changing all the command lines to have two variants (use XX or YY if you have Ninja installed), and we know that the dependency handling works best with Ninja.Fixes #2495