[Geany] Generalisation of build system

[Nick Treleaven]

On Thu, 2 Oct 2008 18:51:01 +0200
Enrico Tröger <enrico.troeger at uvena.de> wrote:

> On Thu, 2 Oct 2008 17:35:28 +0100, Nick Treleaven
> <nick.treleaven at btinternet.com> wrote:
> 
> 
> > The compile & build commands are intended as simple commands. But
> > maybe this is confusing to have these two different ways for
> > building.
> 
> This reminds me that I'm wondering already for a long time why I added
> these both commands. Because mainly 'Build' is sufficient.
> I guess there was a reason why I added both but I can't remember :).
> But well, this was about 3 years ago.
> 
> I think basically we could remove the Compile command. The
> distinction between compile and build is mainly only
> present in C and C++ and for quick testing not really necessary. Build
> should be enough.
> So we could remove the Compile command and replace it with Build, this
> would also avoid confusion about their difference.

I think it would be better have a number of commands the user can run.
But I don't know how to make a custom label get translated (e.g. can it
be translated from a filetypes.foo data file?).

It might upset people to lose a command because for e.g. Python people
might use it to compile the file, checking for errors. Maybe the build
command is less intuitive in that instance, or maybe the user wants the
build command for something else.

One idea could be that compile, build, make, make object are all just a
variable list of commands to run, so essentially the same to Geany. Some
are related to the filetype, some could be global commands available
whatever the filetype.

Regards,
Nick