Clifford Slocombe wrote:
> Manish wrote:
>> Hi everyone
>> Can Any one tell me how can i configure win ARM and DEV-C++.
> This document http://www.bloodshed.net/dev/SetDevCPPArm.pdf describes
> how to setup an older version of Dev-C++ with a cygwin build of the
> cross-compiler. The principles can be adapted for Dev-C++ 18.104.22.168 and
> Note that the current version of Dev-C++ supports multiple compiler
> configurations, so you should be able to switch between the
> cross-compiler and the default MinGW/GCC (useful for testing code and
> producing support tools).
> In general, in the Tools->Compiler options dialog, you modify the
> Directories and Programs tabs to point to the equivalent WinARM tools -
> these have the same name as the native tools but are prefixed
> The only problem I have found is that there is no program setting for
> ramlib, which Dev-C++ uses when building static libraries. The solution
> is to rename or copy arm-elf-ranlib.exe to ranlib.exe. However you need
> to be sure that it does not clash with the native ranlib.exe by placing
> it in a path that is not specified in the PATH environment variable, and
> adding that path to Dev's "Binaries" path list.
> Note that the box for creating multiple configurations is at the top of
> the "Compiler" tab dialog on the enclosing "Compiler options" dialog.
> Caution however, for some reason the compiler set is not stored with the
> progect, so you have to set the compiler set under Project->Project
> options->Compiler dialog everytime you load it. If you will only ever
> use Dev-C++ for cross compilation, then you might simply modify the
> default set.
> Note also that the makefiles that Dev-C++ generated (called
> makefile.win) can be called directly from the command line like normal,
> but you will have to set the PATH environment variable to add the WInARM
> binaries path.