gaurav1804

5 ms·

1.
by gaurav1804 4y ago
The build process is faster. There are a number of algorithms running (on several threads) while building. That is where optimisation kicks in.
2.
by gaurav1804 4y ago
Hi! Task runner would not be an appropriate term for this. Since it also defines target based on their modification times. This is what we call a general purpose build system, just like we call Make and Ninja build system. It can do anythin
3.
by gaurav1804 4y ago
Hi! I would like to point out as I have pointed out in comments above, that Beast and CMake (though might look similar) are different tools. Beast is an actual build system, that looks at your beast file and carries out the tasks you have s
4.
by gaurav1804 4y ago
Thanks! That was the idea yeah!... to have more user-friendly syntax :)
5.
by gaurav1804 4y ago
Hi! Thanks a lot!! These are valuable and I am excited to take a look!! Interestingly, some of the things that you mentioned here are things that I discovered while using Make and Ninja purely through experimentation!!! Great work!!
6.
by gaurav1804 4y ago
I'm not really sure what you are pointing at here. But if you are suggesting to have a single C file that has configurations, dependencies and commands to be run while building your project, then that is not a very good idea. Simply be
7.
by gaurav1804 4y ago
Hi! Even so, if you want to compare Ninja with Beast, Beast has much more user-friendly. Ninja itself claims that build.ninja files are not supposed to be written by humans (since they are not always easy to write). But Beast is super frien
8.
by gaurav1804 4y ago
Thanks a ton :)
9.
by gaurav1804 4y ago
Hi! I made a mistake in my previous reply. I forgot mentioning 'pre' as a dependency for 'proj'. I meant something like: build pre: ! echo 'pre script' build proj: pre ! gradle hello This wi
10.
by gaurav1804 4y ago
By 'faster' I mean better build times than Make for a project of particular size. Benchmarking is going on right now, and the difference in performance is clearly visible.
11.
by gaurav1804 4y ago
Hi! You are right in saying that Beast is "conceptually" similar to Make (and Ninja). But it is much faster and much more user-friendly than Make. Second, you are listing tools like cmake and meson. Note that these are NOT build s
12.
by gaurav1804 4y ago
There can be several reasons for that. Say your project doesn't only require gradle but other tools to be run too. Or say there are some post-scripts or pre-process-scripts that need to be run. They can be done easily like: build p
13.
by gaurav1804 4y ago
Hi! Basically it is supposed to do what Make does... but in a faster and more user-friendly way. Note that Make doesn't have the best syntax. But Beast has sort of a 'python' syntax. It supports strings and integers. Variable
14.
by gaurav1804 4y ago
Hi! The reason why you can compile such large amounts of files with only a few lines in a Makefile, is because most of these files might be carrying a pattern in their build rules (like for example most of them are to be compiled in an obje
15.
by gaurav1804 4y ago
Hi! I know I haven't supported my claims in the readme. But if you see the syntax for beast build files, you will see that indeed syntax in beast is much simpler and intuitive. For example, you have strings and integers for variables.
16.
by gaurav1804 4y ago
Thanks! Noted... I will take care of it! Thanks again
17.
by gaurav1804 4y ago
1. Since Beast is new, there are not a lot of examples. Benchmarking is going on and it will take some time. In the mean time, you can take a look at how to write beast build files. 2. You can use it for any project you want if you know wha
18.
by gaurav1804 4y ago
Hi! It is not only for C/C++, but it can be used for any project in general. This is a low level build system which runs your commands in a shell depending on the rules you define in the beast.build file. Think of it as a faster and mo
19.
Show HN: Beast – A Build System(github.com)
27 points by gaurav1804 4y ago|56 comments