Re: Builder, a build system integration for Emacs

["Augustin Chéneau (BTuin)" <btuin@mailo.com>]

Le 23/05/2023 à 13:18, Eli Zaretskii a écrit :
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: BTuin <btuin@mailo.com>,  emacs-devel@gnu.org
>> Date: Tue, 23 May 2023 08:36:13 +0000
>>
>> Richard Stallman <rms@gnu.org> writes:
>>
>>> Isn't "use build systems" what M-x compile does?
>>> Assuming that each bui;d system provides a shell command to invoke it,
>>> M-x compile can run that command and build the package.
>>
>> The issue is not what M-x compile, but that with a lot of modern
>> programming languages the build systems are complex but automatable, to
>> a point that it would be nice if Emacs could detect the necessary
>> information to invoke the right command or sequence of commands.
> 
> You mean, to guess a good value for compile-command?
> 

I realize that my initial message may have not been clear, my apologies.

This is exactly what Builder does: if you want to compile, it will 
detect which build systems are present in the project and provide you 
choices of commands to execute.  You can see that as an autocomplete for 
M-x compile.

After asking you to chose the command, it will actually pass the string 
to the function `compile'.  So it doesn't re-implement anything.
It's just a layer over `compile', to remove repetitive tasks.

I know you can customize `compile-command', but you can only have one 
value by project, you need to set it for each project and you can't 
switch between values.  It doesn't help you if you want to switch to 
debug or another target, or to run tests, or if you have multiple build 
systems on your project.


I hope it's easier to understand!