[Geany] Specified compiler in custom filetype doesn't work

[Lex Trotman]

On 7 May 2011 09:40, Eugenio Rustico <jfrusciante at tiscali.it> wrote:
> 2011/5/7 Lex Trotman <elextr at gmail.com>:
>>>
>>> In the build menu I see: make, compile custom target, compile (there
>>> is no "build" item); all these three launch a "make" command.
>>
>> So why do you think that the [build_menu ] settings worked if it isn't
>> in the menu?
>
> Above the standards, I see "nvcc" voice, working (it executes nvcc as
> I specified in the config). I was listing the "standard" build
> commends. After those, there are "next error", "prev error", "execute"
> and so on.
>
> Which voice is supposed to execute the commands specified in
> [build_settings]? "Compile" (that insteads calls a make) and "Build"
> (but I see no build voice when a .cu file is loaded)?
>

Basically you shouldn't mix the two sets of build settings.  Geany
will try to combine them in a sensible manner, but as their semantics
differ, it doesn't always work.

You should define all your menu and the commands using [build_menu].
The cheats method is to remove all build settings from your cu
filetype file load a cu file in Geany then define the menu in the Set
build Commands dialog, close Geany (unless you are using the *very*
latest SVN) and the settings will be written to your user cu filetype
file.

As to why your make object menu item has changed name to compile, see
if it has been edited in the set build commands dialog (click on clear
to return to the default).

Cheers
Lex