Re: [Dev-C++] Re: [Dev-C++] DevCpp doesnt work with ARM-oriented
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
From: Ferdinando F. <s2...@st...> - 2003-11-24 12:18:45
|
On Sat, 22 Nov 2003, wugang wrote: Well, than I can't say more: I never experienced something like that. > There are two IDEs installed in my computer. One is hitool, an off the shelf > IDE for arm embedd system. It uses arm-elf-gcc and arm-elf-ld to build > projects. And, in c:\hitool.arm\Compiler\pc-cygwin\bin\, only there is > make.exe, no arm-elf-make.exe. Ops, sorry, I meant just it... > > When hitool works, I can see the command line it uses to call arm-elf-gcc and > arm-elf-ld. > Thus, in 'Log' in Dev-C++ (at least in 5, I just don't remember about 4) you should find the same thing: you can compare the two outputs > You said "It calls make clean to let make delete all outdated files of > previous compilations", but I dont know why in hitool the compiler > doesnt need clean. No clean.exe in the subdirectory. Well, clean isn't a file: a makefile is a file who tells, in a standard syntax, what to do when called to perform one or more operations. It is an old but efficient way to do what modern compilers call a 'project': in a makefile you can specificate what compiler to call, dependencies about sources, and it is customary to include in a section named 'clean' the commands to run when user need to refresh compilation outputs (tipically the *.o files). If you type 'make clean', make.exe simply searches in the makefile the line 'clean:' to know what to do. Dev-C++, who is designed to interface itself with GNU-style compilers, tipically translates your project in a makefile named Makefile.win and then invokes your compiler's make to build it: make knows what compiler to call, because Dev-C++ wrote it in the makefile. I hope you have this file: I don't remember what version of Dev-C++ you were using, and don't know its behaviour under Win98 (I use XP). If you find it and have some experience with unix shells' syntax (at least in environment var definition) you should see something you can understand. > And, why there is > "D:\cygwin\" before the path I input? To me it makes no sense. I never experienced something like that in Win98 > > Greetings. > > Wugamp > Hope I helped. Bye. Ferdinando |