5 ms·

What about Meson? Apart from CMake it's the build system I've seen the most recently. Personally enjoy it a lot. Popularity of tools at least for me is always a

What about Meson? Apart from CMake it's the build system I've seen the most recently. Personally enjoy it a lot. Popularity of tools at least for me is always a consideration since it means it's easier to get help from other people or assemble a team of contributors to a project.

bitwize 4y ago
But it's not statically typed. Good luck building anything bigger than a toy without static typing.
- doodlesdev 4y ago
  A toy such as... DXVK, elementaryOS, Geary, GTK, almost any GNOME application, GStreamer, i3, libfuse, libcamera, Mesa, MPV, Cisco's OpenH264, PipeWire, PostgreSQL, Qemu, SciPy or systemd? I guess our definitions of what's a toy are different :) Take a look at a list of projects using Meson here: https://mesonbuild.com/Users.html https://mesonbuild.com/Users.html
Rochus 4y ago
Meson did indeed some things better than cmake, and I seriously evaluated and considered it for my projects; but on the other hand it's still a dynamic language and has quite some peculiarities, and after analyzing many projects using Meson, where people have used work-arounds against the intent of the language, I decided to come up with my own proposal. Meson also depends on Python which hinders ab initio bootstrap (a major goal of BUSY), and the non-Python versions are not fully compatible or not cross-platform.
- andai 4y ago
  Not sure if this is the right place to mention this, but the Python keyword activated my neurons: upon running LeanCreator.exe I was greeted with two error boxes: lldb-vscode.exe - System Error: The code execution cannot proceed because python310.dll was not found. lldb.exe - System Error: The code execution cannot proceed because python310.dll was not found. This occurs every time the program is run, though the program does indeed start, although I haven't been able to test it much since I'm not very familiar with Qt and Qt Creator. Edit: I'm trying to create a Hello World. File> New File Or Project only lets me "import" one, so I "imported" an empty folder. Nothing seems to happen in the UI (there is no indication that a project has been created or opened, projects button is greyed out, and I can't find a way to add cpp files), though it did create a bunch of project files in that folder.
  - Rochus 4y ago
    The file and project wizzard is on the todo list (see readme); I recommend you download e.g. the LeanQt source and open the top-level BUSY file with LeanCreator to experiment. Concerning "lldb-vscode.exe": I never saw this and don't know what it means; maybe LeanCreator has found an Clang/Lldb installation somewhere which is compiled with Python support, but Python is not in the path; it's possible that you get this error on start because LeanCreator tries to get information about the toolchains it finds by running the programs; you likely get rid of this error if you put the Python executable in the PATH before starting LeanCreator.
    - andai 4y ago
      So I indeed got the same error when running lldb, so I upgraded my llvm from 14 to 15*. This did not solve the error, so I installed Python 3.10 and put it on the path. Now launching LeanCreator takes 26 seconds (nothing appears to happen, so I thought it was broken, but after a long time the window appears) but there are no error boxes anymore. Edit: followed your suggestion. 01:59:38: Running steps for project LeanQt... Error while building/deploying project LeanQt (kit: Desktop) When executing step "Busy Build"
      - Rochus 4y ago
        Oops, that's not a good trade-off; does it always take that long when you start LeanCreator on your machine, or was it - as I would expect - only the first time it required to locate the debugger? If it repeats with each start I should add an option to disable this search or reduce the timeout. Can you try whether it also takes that long if you directly start lldb on the command line?
        andai 4y ago
        lldb starts instantly. For LeanCreator, the delay is there every time: I just used a stopwatch, it was at least 31 seconds.
        4y ago

bitwize 4y ago

But it's not statically typed. Good luck building anything bigger than a toy without static typing.

doodlesdev 4y ago
A toy such as... DXVK, elementaryOS, Geary, GTK, almost any GNOME application, GStreamer, i3, libfuse, libcamera, Mesa, MPV, Cisco's OpenH264, PipeWire, PostgreSQL, Qemu, SciPy or systemd? I guess our definitions of what's a toy are different :) Take a look at a list of projects using Meson here: https://mesonbuild.com/Users.html https://mesonbuild.com/Users.html

Rochus 4y ago

Meson did indeed some things better than cmake, and I seriously evaluated and considered it for my projects; but on the other hand it's still a dynamic language and has quite some peculiarities, and after analyzing many projects using Meson, where people have used work-arounds against the intent of the language, I decided to come up with my own proposal. Meson also depends on Python which hinders ab initio bootstrap (a major goal of BUSY), and the non-Python versions are not fully compatible or not cross-platform.

andai 4y ago
Not sure if this is the right place to mention this, but the Python keyword activated my neurons: upon running LeanCreator.exe I was greeted with two error boxes: lldb-vscode.exe - System Error: The code execution cannot proceed because python310.dll was not found. lldb.exe - System Error: The code execution cannot proceed because python310.dll was not found. This occurs every time the program is run, though the program does indeed start, although I haven't been able to test it much since I'm not very familiar with Qt and Qt Creator. Edit: I'm trying to create a Hello World. File> New File Or Project only lets me "import" one, so I "imported" an empty folder. Nothing seems to happen in the UI (there is no indication that a project has been created or opened, projects button is greyed out, and I can't find a way to add cpp files), though it did create a bunch of project files in that folder.
- Rochus 4y ago
  The file and project wizzard is on the todo list (see readme); I recommend you download e.g. the LeanQt source and open the top-level BUSY file with LeanCreator to experiment. Concerning "lldb-vscode.exe": I never saw this and don't know what it means; maybe LeanCreator has found an Clang/Lldb installation somewhere which is compiled with Python support, but Python is not in the path; it's possible that you get this error on start because LeanCreator tries to get information about the toolchains it finds by running the programs; you likely get rid of this error if you put the Python executable in the PATH before starting LeanCreator.
  - andai 4y ago
    So I indeed got the same error when running lldb, so I upgraded my llvm from 14 to 15*. This did not solve the error, so I installed Python 3.10 and put it on the path. Now launching LeanCreator takes 26 seconds (nothing appears to happen, so I thought it was broken, but after a long time the window appears) but there are no error boxes anymore. Edit: followed your suggestion. 01:59:38: Running steps for project LeanQt... Error while building/deploying project LeanQt (kit: Desktop) When executing step "Busy Build"
    - Rochus 4y ago
      Oops, that's not a good trade-off; does it always take that long when you start LeanCreator on your machine, or was it - as I would expect - only the first time it required to locate the debugger? If it repeats with each start I should add an option to disable this search or reduce the timeout. Can you try whether it also takes that long if you directly start lldb on the command line?
      - andai 4y ago
        lldb starts instantly. For LeanCreator, the delay is there every time: I just used a stopwatch, it was at least 31 seconds.
        4y ago