Shalom SJ wrote:
> I use DevC Ver 4.9.9.2 environment With Winarm.
This is for an older version of Dev-C++ but can be adapted:
http://www.bloodshed.net/dev/SetDevCPPArm.pdf
You can specify the paths to the binaries, libraries and include files
within the IDE, you don't need environment variables.
With careful set-up you can get Dev-C++ to generate makefiles and build
teh code for you rather than using custom makefiles. You can extend the
generated makefile with an 'include' file defining the before-all and
after-all rules. These allow you to perform any necessaty pre- and
post-processing - for example, invoking download tools, or conversion to
a hex rom image.
One problem with Dev-C++ occurs when using the static library project
template, it invokes ranlib but there is no method of specifying
arm-elf-ranlib. The solution is simple, copy arem-elf-ranlib.exe to
ranlib.exe.
Another issue is Dev's insistance of adding a .exe extension to your
output file. You can specify a different filename on a per-project
basis, or use the after-all rule to rename or copy the file.
I'd also recommend using the Tools menu customisation feature to
'integrate' Insight, since I am not certain it is possible to coerce
Dev's integerated debugger to use arm-elf-gdb in any way that makes
sense! The integerated debugger interface is next to useless in any
event!
Clifford
Watch this topic
Disable multi-page view