Possibility to support another compiler (Pelles C)

[RJP Computing]

calm calm.

Oh I am not mad, just wanted to restate what I meant. 

If we can support another compiler (so not debugging), then that's a good thing. Several of the compilers we support have their own IDE (eg . M$ , Borland, Watcom, Intel ,..), but if you can stay within the same IDE when working on different projects, it's nice. Plus also for CB it's nice to have a wide support. But let's take step for step, since it is difficult to know all compiler settings, and the logic has to be simple (eg : mutual exclusive settings, we don't do that), so you tick a whole bunch of options where the compiler might tell you in then end the mix is not correct. But we offer the settings, the user with sound knowledge ticks what he wants.
So once we have a substantial set of settins for a compiler we can start and later on adjust or expand.

Sounds like a great idea.

EDIT:
Thanks SethJackson 

[sethjackson]

calm calm.

Oh I am mad, just wanted to restate what I meant. 

I think you mean not mad.

[MortenMacFly]

If we can support another compiler (so not debugging), then that's a good thing.
[...]
So once we have a substantial set of settins for a compiler we can start and later on adjust or expand.

I still maintain support for the LCC (both, LCC and the Matlab LCC) compiler in the backhand (works fine for me)... but mandrav told me better not to commit due to some remaining issues that should better be fixed inside LCC itself. Just to let you know and to prevent from re-inventing the wheel.
With regards, Morten.

[skirby]

I have done a complete list of all Pelles C command line tools.

I have contact the author in order to know all necessary and optional command line tools.
You can find the result in a Word document here:
http://www.mytempdir.com/1254553

Is it sufficient for you to integrate Pelles C compiler into Code::Blocks?

I you think that my document is incomplete or useless, please let me know what you would like and I will update the document.
I have joined the help file in the zip archive.

If you need help to test the integration, I am your man 

Have a nice day.


Edit: Word document link update

[MortenMacFly]

I have done a complete list of all Pelles C command line tools.

Looks good to me. One question I have: There is a POASM tool included. Is it common to write ASM code in development or is this just some special case?
Why I'm asking: I wonder how to attach the ASM compiler nicely. (You know: C::B is primary a C/C++ IDE). I could imagine to use the C++ compiler therefore... but this may lead to some misunderstanding. Otherwise I'd rather skip this ASM stuff.
With regards, Morten.

Ps.: Oh: And why is "POBIND" useless?!

[skirby]

Writting full asm code could be very nice in some case.
More, it is one of the nice feature of Pelles C compiler.

Isn't it possible to simply add a ASM compiler entry into "Program Files" tab like "C ompiler", "Debugger" or "Resource compiler"
But if you can't or don't want to integrate POASM, I will respect your choice.

POBIND seems not to be necessary.
Here is the answer from the author about POBIND:

POBIND can be used to (possibly) decrease the startup time of an program by
'patching' the executable file. This will take some work off the Windows
loader. It's an optimization that few programs need. And since it's an
optimization, it's never *needed*...

But, how can you integrate this POBIND tool into Code::Blocks?
Where are you putting this tools into Compiler and Debugger setting window?

[killerbot]

we are gonna add a asm program in the set of programs, and register assembler exentions (.s)
But first some other things ;-)

[skirby]

Is my Word document about Command line tools and options OK for you killerbot?

Do you need more informations about Pelles C compiler?

[killerbot]

good enough info, now finding time to implement and test ;-)

[skirby]

I am your man if you need some testers 
Please, let me know when you will be ready and I will be glad to help you.

[skirby]

Hello,

I would like to try to add Pelles C compiler by myself into C::B

So I begun by duplicate a compiler in menu "Settings" and "Compiler and Debugger"
I have modified "Search directories" and "Toolchain executables" but now, what is the way to modify compiler settings ?

If I have a parameter like this:
/V<n> : Set verbosity level 0, 1 or 2 (default: n = 0)

Do I have to create three entries like that:
/V0 : Set verbosity level 0
/V1 : Set verbosity level 1
/V1 : Set verbosity level 2

or is it possible to create an entry where I could enter my value ?

Also, what is the way to manage an option like this:
/I<path> : Add a search path for #include files


Thanks in advance and have a nice day.