Compiler Options Can't Be Deleted!!

[SeanRamey]

CodeLite Version: 9.0
NOT self compiled.
Windows 7 64bit
NASM 2.11.09rc1

I'm am trying to use CodeLite as an IDE for x86 assembly using the NASM assembler. All I need to do is add NASM as a compiler and supply it with the correct build commands, but, first of all, there seems to be no way to make a new blank compiler! I tried "Add an existing compiler" but it does absolutely nothing when I give it the NASM folder. So I'm stuck with cloning TDM-GCC-32. I want to delete and clear out all of the options associated with GCC so I tried to delete everything. It seems to work, until I click apply and ok and then exit the build settings; but when I re-enter the build settings, everything is back!!! CodeLite will not let me delete the compiler options at all!

Also, the documentation is pretty useless... Is there a list somewhere that tell you all of the available $(thingyHere) options for the file types tab so that I can add a custom build for NASM?

[SeanRamey]

So I guess nobody knows anything to help me? Am I posting this in the right area?

[eranif]

CodeLite will not let me delete the compiler options at all!

I am not sure what you mean, but whats wrong with having the CXX, CC etc set?

So I'm stuck with cloning TDM-GCC-32. I want to delete and clear out all of the options associated with GCC so I tried to delete everything. It seems to work, until I click apply and ok and then exit the build settings

I am not sure which version you used, but it works now.
Settings->Build Settings->Compilers->Add a compiler->Clone a compiler

Give the compiler a name and in the "Copy settings from" field, leave it with "<None>"
You can delete all options and they will stay "clean"

NOTE:
When you stand on each of the field, you get a doc at the bottom (see screenshots)

To alter the build command, go to the 'File Types' tab and edit the file that ends with '.s' (unless you have different extension for nasm files)

nasm.png

nasm2.png

Eran

[SeanRamey]

Hey, thanks for the repsonse eranif!

I didn't see the "Help" button in the file types settings, so thanks for that info! But anyways, I tried the "Clone a compiler" -> "None" -> delete all compiler options, but it still doesn't work for me. After I delete anything, click apply, close build options and reopen build options, all the compiler options are back. Heck, it will reload the compiler options back if I just click apply and select another compiler, then reselect the one I deleted all the options for. But, actually, it really doesn't matter anyways since the compiler options do absolutely nothing! I thought it was similar to code::blocks where you have global compiler options in the build options menu, and you just toggle which ones you want on and off. (Try code::blocks global compiler options and you will see what I mean. Funny thing though, code::blocks is also buggy in the global compiler options.) So what is the point of the compiler options in the build options? It just seems to be a reference for you to use when you want to manually add compiler options to the project build options.

I did get NASM up and running now, but these are still bugs I assume, and they really should be fixed. Also, I'm using version 9.1.3 now, and it still has these problems.

[eranif]

I am sure that we only have a problem with communication:
Can you please explain (using screenshot) which "Compiler options" can't be deleted? so I can try and reproduce (and fix this) here?

Thanks
Eran

[SeanRamey]

Here is a video of the problem. CodeLite v9.1.4

http://www.filedropper.com/desktop04212016-03335101

First of all, in the video I selected add a new compiler->clone a compiler->copy settings from <none>. So, if it copied the settings from <none> then why does it give me the default options for the MinGW compiler?

Second, just like I said, after deleting a compiler option, clicking "apply" and deselecting and reselecting the compiler, the options are all back.