[Geany-devel] Build system status update
nick.treleaven at xxxxx
Mon Feb 1 18:22:57 UTC 2010
On Tue, 26 Jan 2010 17:00:48 +1100
Lex Trotman <elextr at gmail.com> wrote:
> > Just wondering how much work this would be - would this be a full
> > reworking?
> In principle no, the general functionality will be the same, but in
> the details (the devil :) probably bits of everything in build.c are
> affected. I am also trying to reduce dependence from other parts of
> Geany once the interaction with the current implementation is removed.
> Attached is a spec/design doc I'm using to remind me what is needed.
> The requirements section is ok, ATM the design section is just notes
> to self. It will expand. In the future it may be worthwhile putting
> this somewhere later maintainers can access it Where do you think,
> the doc directory?.
Yes, IMO it would be OK in doc/.
> > BTW I may have sounded too strict about the plugin API, this isn't
> > something to worry about too much (we can break the ABI when we want).
> Thats ok, but lets get it right and just do it once :-)
> > IMO I'm quite happy with the new build system, we just need to iron out
> > any issues users have with it.
> The reason I'm doing this is that there are a couple of issues that I
> have with it. I'm probably pushing it harder than most users but
> eventually others will run into the same issues.
> 1. GUI issues
> a. some things that matter (to me at least) are not GUI configurable
> b. the GUI split between project and build sections makes it hard to
> tell what is going on overall
> 2. internal functionality is poorly supported, shows up in
> a. difficulty accommodating plugin interface
> b. built in browser functionality has to be invoked by "magic" commands
> c. see 3.e. below
> 3. some functionality is dependent on where an item is in the menu
> a. custom target dialog is always item 3 section 2, even if I don't
> want it
> b. only execute commands are stopable
> c. parsing of command output for sections 1 & 2 always
> d. no ability to execute commands without a terminal or parse.
> e. fixed positions of next/prev error and dialog items
> Gee that looks a long list now I've writen it down :-)
Ok, good luck ;-)
More information about the Devel