User forums > Using Code::Blocks

Using code:blocks with iar compiler

(1/2) > >>

mastupristi:
I want to use Code::Blocks with iar compiler (it is for NEC microcontrollers).
How can I configure Code::Blocks to use this compiler?

thanks

mandrav:
I haven't got a clue  :roll: . Never used it...

Nevertheless, you can give it a try:
Create a copy of an existing compiler in codeblocks and edit its advanced options. If you get it working, wait for the next release where you can configure even the way the compiler's output messages are parsed :)

Yiannis.

mastupristi:

--- Quote from: mandrav ---I haven't got a clue  :roll: . Never used it...
--- End quote ---

We use it to program the 8 bit microcontroller from NEC.


--- Quote from: mandrav ---Nevertheless, you can give it a try:
Create a copy of an existing compiler in codeblocks and edit its advanced options. If you get it working, wait for the next release where you can configure even the way the compiler's output messages are parsed :)
--- End quote ---


BTW, where can I find documents about writing a plug-in?

thanks

mandrav:

--- Quote ---BTW, where can I find documents about writing a plug-in?
--- End quote ---

I 'm currently writing a tutorial on the subject. It will be released with the next update because it uses the updated SDK from CVS.

Yiannis.

moosewoler:
i have set up code::blocks(10.05) co-work with IAR for msp430 (5.10) to compile files.
just follow several steps:
i.  new a complier setting
ii. modify complier options
iii. set up output parsing to grab output message

i. new a complier setting
Setting-> Compiler and Debugger
just Copy a complier setting from Global Compiler Setting. everyone is ok. I copied "Borland C++ Compiler" for instance.
rename the copied item to "IAR for msp430 5.10"
ii. modify compiler options
IAR uses "icc430.exe" to compile, and "xlink.exe" as the linker
switch to "Toolchain Executables" tab to fill in the correct compiler and linker.(PS, i have find the debugger:( ). and set the correct IAR installation path ("D:\IAR Systems\Embedded Workbench 6.0 Evaluation\430" for example)
add search paths into "Search Directories" tab
uncheck all compiler flags in "Complier settings" tab. and fill "--no_wrap_diagnostics --only_stdout" into "other options". this compiler flag can make every compiler output item in a single line, and disable stderr output.
iii. set up output parsing to grab output message
go to "Other Settings" and click "Advanced Settings.." below.
In "Commands" tab
fill "$compiler $options $includes -o $object $file"
In "Output Parsing"
set Compiler Warning Regular Exp to (^".*"),([0-9]*).*Warning(.*)[^.](.*)
set Compiler Error Regular Exp to (^".*"),([0-9]*).*[eE]rror(.*)

ok, code::blocks now can compile files using IAR toolchains. You can also quick locate the error lines and warning lines from "Build Messages"

Navigation

[0] Message Index

[#] Next page