[Geany] Generalisation of build system

Enrico Tröger enrico.troeger at xxxxx
Mon Oct 6 12:51:47 UTC 2008


On Fri, 3 Oct 2008 15:14:19 +0100, Nick Treleaven
<nick.treleaven at btinternet.com> wrote:

> 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?).

No idea, maybe we could use intltool for this, similar to the way
the .desktop gets translated but this has just to be tested.


> 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.

Sorry, I wasn't clear on this.
I didn't mean to remove the Compile command. Rather I meant to replace
the Compile command of C-like filetypes (those which actually use
Compile&Build) with the Build command and then drop the additional
Build command, i.e. Compile for C-like filetypes does Build, Compile
for other filetypes, like Python remains as it is.


> 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.

This would be even better, so if we make those commands more flexible,
we don't need to discuss the above  :).


Regards,
Enrico

-- 
Get my GPG key from http://www.uvena.de/pub.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.geany.org/pipermail/users/attachments/20081006/d5fa6f38/attachment.pgp>


More information about the Users mailing list