bbrady1992's answer works for me.
In Centos,
$ sudo yum install geany-devel
solves:
"checking for GEANY... configure: error: Package requirements (geany >= 1.26)
were not met:
No package 'geany' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a
I had a look at the code in ```build.c``` and tried to understand what it's
doing. This is how I understood it:
If someone (a plugin) wants to re-write the build menu it would have to call
```build_menu_update``` and then the menu items are re-written according to the
magic/selection process
> If we want to add plugins to be a build command source we would need to
> define a new GeanyBuildSource, e.g. GEANY_BCS_PLUGIN.
Correct
> So e.g. exec_proj holds the commands for the prjoject and does not point to
> one command but to an array of 9 commands (maximum?).
It points to the
> You mean the Set Build Commands dialog I guess. My thought was that plugin
> commands NOT be set there, just shown as insensitive since they are the
> highest priority.
> These pointers are not and should not be exposed, they are Geany
> implementation details. Thats another reason not to
