Earlier quoted context omitted.
Python as in Scons? Otherwise I don't understand your comment.
Scons is effectively dead, and I wish people would start removing it from the Python build systems web pages. Meson is written in Python and isn't dead. However, Meson requires a partner to actually build things--something like cmake or ninja. However, I think the original poster meant "Why Lua instead of Python?" And the only real answer is "Because that's what the author wanted to use."
Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
11–20 of 57 posts
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#12Looks cool, but is there a tl;dr for why I’d use this instead of something like Bazel?
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#13Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#14Looks cool, but is there a tl;dr for why I’d use this instead of something like Bazel?
I haven't compared it to bazel, but if you like the description style of xmake for the project or you like lua, you can try it.
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#15Earlier quoted context omitted.
Python as in Scons? Otherwise I don't understand your comment.
Scons is effectively dead, and I wish people would start removing it from the Python build systems web pages. Meson is written in Python and isn't dead. However, Meson requires a partner to actually build things--something like cmake or ninja. However, I think the original poster meant "Why Lua instead of Python?" And the only real answer is "Because that's what the author wanted to use."
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#16Earlier quoted context omitted.
I haven't compared it to bazel, but if you like the description style of xmake for the project or you like lua, you can try it.
You should definitely take a look at bazel. This is not say bazel is better than the one you wrote but cleary bazel is becoming a industry standard making other build tools obsolete.
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#17Looks cool, but is there a tl;dr for why I’d use this instead of something like Bazel?
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#18Xmake has its own package management repository. https://github.com/xmake-io/xmake-repo And it also supports self-built distributed repositories and third-party repositories (e.g. vcpkg, conan, clib, homebrew). add_requires("libuv master", "ffmpeg", "zlib 1.20.*") add_requires("tbox >1.6.1", {optional = true, debug = true}) target("test") set_kind("shared") add_files("src/*.c") add_packages("libuv", "ffmpeg", "tbox",…
yaourt xmake
section of the install section (the Arch Linux instructions).Yaourt is no longer actively maintained and poses security risks. Just linking to the AUR package is usually enough.
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#19Xmake has its own package management repository. https://github.com/xmake-io/xmake-repo And it also supports self-built distributed repositories and third-party repositories (e.g. vcpkg, conan, clib, homebrew). add_requires("libuv master", "ffmpeg", "zlib 1.20.*") add_requires("tbox >1.6.1", {optional = true, debug = true}) target("test") set_kind("shared") add_files("src/*.c") add_packages("libuv", "ffmpeg", "tbox",…
Just as a heads up, you should probably remove the yaourt xmake section of the install section (the Arch Linux instructions). Yaourt is no longer actively maintained and poses security risks. Just linking to the AUR package is usually enough.
Re: Show HN: A Modern C/C++ build tools (Simple, Fast, Cross-platform)
#20Earlier quoted context omitted.
Python as in Scons? Otherwise I don't understand your comment.
Scons is effectively dead, and I wish people would start removing it from the Python build systems web pages. Meson is written in Python and isn't dead. However, Meson requires a partner to actually build things--something like cmake or ninja. However, I think the original poster meant "Why Lua instead of Python?" And the only real answer is "Because that's what the author wanted to use."