On 22 January 2014 23:19, Tim Black <tblack@actia.co.uk> wrote:
Hi thanks for getting back to me.

Maybe I should have been a little more specific in my requirements:

My folder structure looks like:

/APPS
        /application1
                /src
        /application2
                /src    <- geany pointing to file here !  See note below

Not sure what you mean by "pointing to here", do you mean 1) currently editing a file here, 2) Geany was started with here as pwd, 3) the wd of the make command is explicitly pointed here, or something else?

In each case 

1) your command could be a script that is passed %d as an argument and then extracts the tail and prefixes it with /build1.  That is a single script and it doesn't even need to be in the application dir and can be filetype independent and an absolute path.

2) a filetype independent build command runs a script (from the local dir) that knows to run the matching make in /build1/... This needs a script in each application dir.

3) if its explicit, you might as well make it explicit to build1/... dir

You should probably also be looking at projects which can also set build commands and be more specific.

Personally I would use 2) having a hard wired script in each application dir, its simple, its explicit so the next maintainer can understand it, and it doesn't depend on Geany specifically so you can also run the script from the command line as well.  Sure it will take half an hour to set up twenty scripts, but then its done :)

Cheers
Lex
 
        /application3
                /src

... 20 or so applications ...

/buid1
        /application1
                /src
        /application2
                /src    <- I want geany to execute the Makefile here
        /application3
                /src

... 20 or so applications ...

If I put a makefile (e.g. Makefile.geany) in /APPS/application2/src that points to the makefile in /build1/application2/src then regardless of which directory the file I am editing is the Make command will pick up the Makefile.geany and build application2.  Obviously each Makefile.geany file would need to be customised to execute the correct target.

My question is:

What would I put in the Makefile.geany to run make in ../../build1/application/src or would a shell script (geany.make) be more sensible that simply executed e.g. pushd ../../build1/application/src; make; popd;  Every directory would have the geany.make script so I can simply have to put geany.make in the command settings.

Your comments on the best course of action would be appreciated.

Thanks again

Tim
[...]