Forum: ARM programming with GCC/GNU tools DevC enviorment With Winarm

 Author: Shalom S. (shalomj) Posted on: 2006-03-12 23:20

Rate this post
 0 ▲ useful ▼ not useful
I use DevC Ver 4.9.9.2  environment With Winarm.
I only specified the make option and worked on directories of WINARM
examples.
It works nice! Thanks!
How can i specify the path of winarm\bin will be included in make file.
Now i add this paths to Autoexec.bat  file on WIN98.
With path specifying in make file new installations will be very easy !
More nice will be the make file generator inside the DevC!
Thanks again !

 Author: Martin Thomas (Guest) Posted on: 2006-03-18 18:36

Rate this post
 0 ▲ useful ▼ not useful
Shalom SJ wrote:

> How can i specify the path of winarm\bin will be included in make file.

You can extend the "filenames" of the tools with the path. For example:
CC = c:/WinARM/bin/arm-elf-gcc

> Now i add this paths to Autoexec.bat  file on WIN98.

I have not used Win9X for a long time. But adding a line like
PATH=%PATH%;C:\WinARM\bin;C:\WinARM\utils\bin to autoexec.bat should
work.

> With path specifying in make file new installations will be very easy !
> More nice will be the make file generator inside the DevC!

Feel free to write a small tutorial. I'm currently not using Dev+C++ but
I will include your tutorial in the next WinARM.

Hope this helps,
Martin Thomas

 Author: Clifford S. (clifford) Posted on: 2006-04-19 01:32

Rate this post
 0 ▲ useful ▼ not useful
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
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

• Post long source code as attachment, not in the text

Formatting options

• [c]C code[/c]
• [avrasm]AVR assembler code[/avrasm]
• [code]code in other languages, ASCII drawings[/code]
• $formula (LaTeX syntax)$
 Name: E-mail address (not visible): Subject: Searching for similar topics... Attachment: Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one. Text: