Thread: [Dev-C++] [RELEASE] Dev-C++ 4.9.3.0 beta available !
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
Menu
▾
▴
dev-cpp-users
|
From: Colin L. <col...@wa...> - 2002-05-14 00:45:30
|
Hi !! Here it is ! the new Dev-C++ beta :) This one should really be far more stable than previous 4.9.2.0. Here is what's new : * Lots of bugfixes !! * More stable class browser and code completion. * Dev-C++ now displays the current build progress, instead of printing all output when compilation has ended. * New, rewritten conio, for Borland compatibility (read FAQ about how to use it) * A new Package Manager is now included. * Perfect dependency generation; let's say if you have main.c and main.h. If you change something in main.h, main.c will now get recompiled. This slows things down a bit, but can be disabled in Compiler Options. * New syntax checking feature. * New translations: Chinese, Greek, Germand and Spanish. * Swap header/source files in Edit and popup menus * Shortcuts customizing * Selection of project output directory * File associations Please report bugs to sourceforge bug tracker (http://sourceforge.net/tracker/?group_id=10639&atid=110639) or to me at ha...@bl... and to hongli (ho...@te...). We will soon release various packages for using with Dev-C++ (SDL, wxWindows, FLTK...) Enjoy :) Colin |
|
From: Ioannis V. <no...@ho...> - 2002-05-14 02:52:43
|
> -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf > Of Colin Laplace > Sent: Tuesday, May 14, 2002 3:33 AM > To: dev...@li... > Subject: [Dev-C++] [RELEASE] Dev-C++ 4.9.3.0 beta available ! > > > Hi !! > > Here it is ! the new Dev-C++ beta :) > This one should really be far more stable than previous 4.9.2.0. [...] > * New, rewritten conio, for Borland compatibility (read FAQ > about how to use > it) You mean you wrote your own version or a newer MINGW snapshot has this? Ioannis * Ioannis Vranos * Programming pages: http://www.noicys.cjb.net * Alternative URL: http://run.to/noicys |
|
From: Colin L. <col...@wa...> - 2002-05-14 08:58:59
|
Hi, > > * New, rewritten conio, for Borland compatibility (read FAQ > > about how to use > > it) > > You mean you wrote your own version or a newer MINGW snapshot has this? This is the own Dev-C++ version :) made by Hongli Greetings, Colin |
|
From: Ioannis V. <no...@ho...> - 2002-05-14 12:39:43
|
> -----Original Message----- > From: dev...@li... > [mailto:dev...@li...] On Behalf > Of Colin Laplace > Sent: Tuesday, May 14, 2002 11:46 AM > To: dev...@li... > Subject: Re: [Dev-C++] [RELEASE] Dev-C++ 4.9.3.0 beta available ! > > > Hi, > > > > * New, rewritten conio, for Borland compatibility (read FAQ > > > about how to use > > > it) > > > > You mean you wrote your own version or a newer MINGW > snapshot has this? > > This is the own Dev-C++ version :) made by Hongli Congratulations to Hongli. :) Ioannis * Ioannis Vranos * Programming pages: http://www.noicys.cjb.net * Alternative URL: http://run.to/noicys |
|
From: Ricardo R. <ri...@po...> - 2002-05-14 07:57:21
|
Bravo Colin and co-workers!! I read that you are thinking to include several packages with the new version, I want to suggest if it would be possible to include in the new future version, also as a Package, the ALLEGRO library (for video-graphics programming) ??. salutti, Ricardo. |
|
From: Brian P. <br...@su...> - 2002-05-14 15:22:59
|
I Love it! Dev-C++ is really shaping up! I use it quite a bit now. I did notice one thing...a reeeeealy small thing....(in 4.9.3.0)when I compile something the Compile Log (under the tab by that name) says "Execution terminated" and thats all. Now, I realize that if no errors pop up I should be good to go. I also realize that the "Size of Output" txtbox shows me that an exe got made, but...It would be nice if the Compile Log said something like, "project compiled successfully..." or "Hey Boy! You done good!" or "Yeeehaw!" O.k., maybe I am getting a bit carried away. But you get the idea. I know, its stupid, small, and trivial, but hey, must be great to get to a point where the program is so refined that all there is left to do is tweak the trivial stuff purely for asthetics, right? ;-) On Mon, 2002-05-13 at 17:33, Colin Laplace wrote: > Hi !! > > Here it is ! the new Dev-C++ beta :) > This one should really be far more stable than previous 4.9.2.0. > > Here is what's new : > > * Lots of bugfixes !! > * More stable class browser and code completion. > * Dev-C++ now displays the current build progress, instead of printing all > output when compilation has ended. > * New, rewritten conio, for Borland compatibility (read FAQ about how to use > it) > * A new Package Manager is now included. > * Perfect dependency generation; let's say if you have main.c and main.h. > If you change something in main.h, main.c will now get recompiled. > This slows things down a bit, but can be disabled in Compiler Options. > * New syntax checking feature. > * New translations: Chinese, Greek, Germand and Spanish. > * Swap header/source files in Edit and popup menus > * Shortcuts customizing > * Selection of project output directory > * File associations > > Please report bugs to sourceforge bug tracker > (http://sourceforge.net/tracker/?group_id=10639&atid=110639) or to me at > ha...@bl... and to hongli (ho...@te...). > > We will soon release various packages for using with Dev-C++ (SDL, wxWindows, > FLTK...) > > Enjoy :) > Colin > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |
|
From: Luigi S. <gi...@li...> - 2002-05-14 16:17:39
|
Hello list,
I have only limited experience, so probably I'm missing something.
I'm wondering how does Dev-C++ 4.9.3.0 find out that main.c should be
recompiled, when one changes something in main.h.
Anyway I tried to do some test, and the "perfect dependency" idea, seems to
be not working, also I've given a look at the makefile (named
"makefile.win") and did see the name of no header file (that is, no ".h"
file) anywhere.
One thing that seems strange is that the makefile is rewritten each time
one clicks on the "compile" button. IMHO, that should be done:
- the first time one clicks on the compile button ('cause there is no
makefile yet)
- every time the project changes (say you add, delete or rename some file)
- every time one clicks on the rebuild all button
Finally I see no reason why the linker is called each time one clicks on
the compile button, even if no object file was updated (because no source
file did actually change) by the compiler: clearly this action is superfluous.
At 02:33 14/05/02 +0200, col...@wa... wrote:
>Hi !!
>
>Here it is ! the new Dev-C++ beta :)
>...
>Here is what's new :
>...
>* Perfect dependency generation; let's say if you have main.c and main.h.
> If you change something in main.h, main.c will now get recompiled.
> This slows things down a bit, but can be disabled in Compiler Options.
>...
>Enjoy :)
>Colin
--
Luigi
gi...@li...
|
|
From: Hongli L. <h....@ch...> - 2002-05-14 19:11:57
|
On Tue, 2002-05-14 at 18:15, Luigi Santillo wrote: > Hello list, > > I have only limited experience, so probably I'm missing something. > > I'm wondering how does Dev-C++ 4.9.3.0 find out that main.c should be > recompiled, when one changes something in main.h. > > Anyway I tried to do some test, and the "perfect dependency" idea, seems to > be not working, also I've given a look at the makefile (named > "makefile.win") and did see the name of no header file (that is, no ".h" > file) anywhere. > Dev-C++ executes "gcc -MM main.c" and put the output of that into the Makefile, so that make will handle dependencies. However, if the output of gcc -MM contains error messages, it's output will be ignored. You will also have to #include "main.h" into your main.c in order to make this work. > Finally I see no reason why the linker is called each time one clicks on > the compile button, even if no object file was updated (because no source > file did actually change) by the compiler: clearly this action is superfluous. > There's no reason to click on Compile if everything is already compiled anyway. The only reason I can think of is because the user wants to relink the app, that's why I made Dev-C++ behave like that. |
|
From: Luigi S. <gi...@li...> - 2002-05-15 13:07:51
|
Hello Hongli Lai
At 21:15 14/05/02 +0200, Hongli Lai wrote:
>On Tue, 2002-05-14 at 18:15, Luigi Santillo wrote:
> > Hello list,
> >
> > I have only limited experience, so probably I'm missing something.
> >
> > I'm wondering how does Dev-C++ 4.9.3.0 find out that main.c should be
> > recompiled, when one changes something in main.h.
> >
> > Anyway I tried to do some test, and the "perfect dependency" idea,
> seems to
> > be not working, also I've given a look at the makefile (named
> > "makefile.win") and did see the name of no header file (that is, no ".h"
> > file) anywhere.
> >
>
>Dev-C++ executes "gcc -MM main.c" and put the output of that into the
>Makefile, so that make will handle dependencies.
>However, if the output of gcc -MM contains error messages, it's output
>will be ignored.
>
>You will also have to #include "main.h" into your main.c in order to
>make this work.
Thanks for your explanation. It is very clear.
Here are the steps I followed when doing my simple testing of the new
dependency generation feature.
1. The code. Instead of using main.c and main.h I've used: hello.c (main
source), print.h and print.c
hello.c print.h print.c
------- ------- -------
#include "print.h" #ifndef print_h #include <stdio.h>
int #define print_h #include "print.h"
main() void
{ void print(const char* s)
print("Hello world!"); print(const char *s); {
return 0; puts(s);
} #endif }
2. The compiler settings. I suppose the relevant item, here, is:
Tools->Compiler Options->Code Generation/Optimizations->Makefile generation->
"use fast but imperfect dependency generation".
Well, I've left the box not checked (which is the default when installing
the binary version of beta3); so I expect dependencies to be "slow but
perfect".
3. The project. I chose: File->New->Project->Basic->Console Application.
Also I selected "C project". Then named the project "test" and the project
file "test" (so that test.dev was created). Finally I removed the default
"main.c" file and added the 3 files hello.c, print.c and print.h.
When I compiled the project (using the Compile button) here is the
makefile.win generated:
makefile.win
------------
# Project: test
# Makefile created by Dev-C++ 4.9.3.0
CC = gcc.exe
WINDRES = windres.exe
RES =
OBJ = print.o hello.o $(RES)
LIBS = -L"c:\mingw\lib"
INCS = -I"c:\mingw\include"
BIN = test.exe
CFLAGS = $(INCS)-ansi -fexceptions -g3
.PHONY: clean
all: test.exe
clean:
rm -f $(OBJ) $(BIN)
$(BIN): $(OBJ)
$(CC) $(OBJ) -o $(BIN) $(RES) $(LIBS) $(CFLAGS)
print.o: print.c
$(CC) -c print.c -o print.o $(CFLAGS)
hello.o: hello.c
$(CC) -c hello.c -o hello.o $(CFLAGS)
As one can see, print.o depends only on print.c (print.h is missing), the
same is true of hello.o.
In case it can be of help, I'm using MinGW gcc shipped with stable Dev-C++
4.0, that is, the command: "gcc -v" prints "gcc version 2.95.2 19991024
(release)" and the command "gcc -MM print.c" works as you explained (I mean
there is no error, and it prints: "print.o: print.c print.h").
> > Finally I see no reason why the linker is called each time one clicks on
> > the compile button, even if no object file was updated (because no source
> > file did actually change) by the compiler: clearly this action is
> superfluous.
> >
>
>There's no reason to click on Compile if everything is already compiled
>anyway.
That is right. But I was testing :)
>The only reason I can think of is because the user wants to relink the
>app, that's why I made Dev-C++ behave like that.
I do not agree with you for this reason: if I use the program "make" and
try to make an already up-to-date program (that is, I type "make all -f
makefile.win"), "make" answers something like: "nothing needed to be done
for all"; it does not relink the program. I expected the same kind of
behavior when clicking "Compile" from Dev-C++.
Thanks again for your time.
Regards
--
Luigi
gi...@li...
|
|
From: Luigi S. <gi...@li...> - 2002-05-16 17:58:45
|
At 15:52 15/05/02 +0200, Hongli Lai wrote: >Hm... you're right. There's a bug in Dev-C++ parsing code. >I'm going to fix it now. The next version will include the bugfix. Here are two small things which could be worth a little attention: 1. the command "rm" (used to erase files, when making the "clean" target), is not available on old Win98SE, only "del" is implemented there and it expects one argument (so one may erase: a single file or more than one file but only using wildcards). 2. The Execute->Syntax Check, could have an icon so that it may be used more often, and why not consider the command "gcc -c source.c" in place of "gcc -S source.c -o nul"? The former one would generate the object file (if there is no error during the compilation) which would only need to be linked when one cliks on the "Compile" button to build the executable. -- Luigi gi...@li... |
|
From: Hongli L. <h....@ch...> - 2002-05-16 18:58:56
|
Luigi Santillo wrote: > At 15:52 15/05/02 +0200, Hongli Lai wrote: > >> Hm... you're right. There's a bug in Dev-C++ parsing code. >> I'm going to fix it now. The next version will include the bugfix. > > > Here are two small things which could be worth a little attention: > > 1. the command "rm" (used to erase files, when making the "clean" > target), is not available on old Win98SE, only "del" is implemented > there and it expects one argument (so one may erase: a single file or > more than one file but only using wildcards). > > > 2. The Execute->Syntax Check, could have an icon so that it may be > used more often, and why not consider the command "gcc -c source.c" in > place of "gcc -S source.c -o nul"? The former one would generate the > object file (if there is no error during the compilation) which would > only need to be linked when one cliks on the "Compile" button to build > the executable. That would defeat the purpose of "syntax checking". The syntax checking feature is designed to see if the source code has the correct syntax, not to compile it. Otherwise, you may just as well use the Compile button. |
|
From: Hongli L. <h....@ch...> - 2002-05-15 13:49:07
|
Luigi Santillo wrote: > Hello Hongli Lai > > At 21:15 14/05/02 +0200, Hongli Lai wrote: > >> On Tue, 2002-05-14 at 18:15, Luigi Santillo wrote: >> > Hello list, >> > >> > I have only limited experience, so probably I'm missing something. >> > >> > I'm wondering how does Dev-C++ 4.9.3.0 find out that main.c should be >> > recompiled, when one changes something in main.h. >> > >> > Anyway I tried to do some test, and the "perfect dependency" idea, >> seems to >> > be not working, also I've given a look at the makefile (named >> > "makefile.win") and did see the name of no header file (that is, no >> ".h" >> > file) anywhere. >> > >> >> Dev-C++ executes "gcc -MM main.c" and put the output of that into the >> Makefile, so that make will handle dependencies. >> However, if the output of gcc -MM contains error messages, it's output >> will be ignored. >> >> You will also have to #include "main.h" into your main.c in order to >> make this work. > > > Thanks for your explanation. It is very clear. > > Here are the steps I followed when doing my simple testing of the new > dependency generation feature. > > 1. The code. Instead of using main.c and main.h I've used: hello.c > (main source), print.h and print.c > Hm... you're right. There's a bug in Dev-C++ parsing code. I'm going to fix it now. The next version will include the bugfix. |
|
From: <jar...@ig...> - 2002-05-15 08:08:33
|
On 14 May, Colin Laplace wrote: > Hi !! > > Here it is ! the new Dev-C++ beta :) > This one should really be far more stable than previous 4.9.2.0. > Am I the only one who needs to fetch MSYS-1.0.x and copy msys-1.0.dll to C:\Dev-C++\bin ? Or is it Win2000 (SP2) specific? Thanks for the new release Helmut Jarausch Lehrstuhl fuer Numerische Mathematik Institute of Technology, RWTH Aachen D 52056 Aachen, Germany |
|
From: <mr...@c2...> - 2002-05-15 08:44:34
|
> On 14 May, Colin Laplace wrote: > > Hi !! > > > > Here it is ! the new Dev-C++ beta :) > > This one should really be far more stable than previous 4.9.2.0. > > > > Am I the only one who needs to fetch MSYS-1.0.x and copy > msys-1.0.dll to C:\Dev-C++\bin ? > Or is it Win2000 (SP2) specific? Same for me on w98. Oh, and BTW, with v4.x it was possible to use standard help files, and it was possible to just copy these to the help directory of Dev- C++ for easy access from within Dev. For example the Win32 API help file that is distributed with LCC-WIN. This seems to be impossible now, right? And one more thing, the old resource editor at least had some buttons for inserting bitmaps, menus etc. It was crude, but I liked having these buttons to save time writing it all manually. Is it possible to get something similar in the new version? -=D8yvind --------------------------------- mr...@c2... @ work |
|
From: Andres R. <lo...@ho...> - 2002-05-15 21:47:16
|
Hello! From thee other letter/thread Hongli Lai wrote: Hm... you're right. There's a bug in Dev-C++ parsing code. I'm going to fix it now. The next version will include the bugfix. My question is: can't you make 'snapshots' to get mid-fixed versions? For example 4.9.3.1 ;) I checked Bloodshed website and 4.9.2.0 wos released exactly 1 month ago. So, wating a new release (alpha, beta, gamma or waht ever) to get some bugs fixed is kinda long IMHO. Andres. |
|
From: Hongli L. <h....@ch...> - 2002-05-16 19:12:29
|
Andres Rand wrote: >Hello! > >>From thee other letter/thread Hongli Lai wrote: > Hm... you're right. There's a bug in Dev-C++ parsing code. > I'm going to fix it now. The next version will include the >bugfix. > >My question is: can't you make 'snapshots' to get mid-fixed versions? >For example 4.9.3.1 ;) >I checked Bloodshed website and 4.9.2.0 wos released exactly 1 month >ago. So, wating a new release (alpha, beta, gamma or waht ever) to get >some bugs fixed is kinda long IMHO. > >Andres. > > You can download the lastest development version from CVS. |
|
From: <ste...@ge...> - 2002-05-16 15:52:09
|
I have a question about the new realease... I compile my project, and then if I want to compile straight after again the compiler says; "cannot open output file Clod.exe D:\Dev-C++_4930\mingw32\bin\ld.exe - Permission denied" Then I wait for a while (maybe 10secs or so), and then it compiles fine again. What's the reason for this? I can't either delete my exe until a few second after compilation.. Thanks! - Stein Nygård - http://null.dk/~stein ----- Original Message ----- From: "Colin Laplace" <col...@wa...> To: <dev...@li...> Sent: Tuesday, May 14, 2002 2:33 AM Subject: [Dev-C++] [RELEASE] Dev-C++ 4.9.3.0 beta available ! > Hi !! > > Here it is ! the new Dev-C++ beta :) > This one should really be far more stable than previous 4.9.2.0. > > Here is what's new : > > * Lots of bugfixes !! > * More stable class browser and code completion. > * Dev-C++ now displays the current build progress, instead of printing all > output when compilation has ended. > * New, rewritten conio, for Borland compatibility (read FAQ about how to use > it) > * A new Package Manager is now included. > * Perfect dependency generation; let's say if you have main.c and main.h. > If you change something in main.h, main.c will now get recompiled. > This slows things down a bit, but can be disabled in Compiler Options. > * New syntax checking feature. > * New translations: Chinese, Greek, Germand and Spanish. > * Swap header/source files in Edit and popup menus > * Shortcuts customizing > * Selection of project output directory > * File associations > > Please report bugs to sourceforge bug tracker > (http://sourceforge.net/tracker/?group_id=10639&atid=110639) or to me at > ha...@bl... and to hongli (ho...@te...). > > We will soon release various packages for using with Dev-C++ (SDL, wxWindows, > FLTK...) > > Enjoy :) > Colin > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |
