What do you want to do? If you want to help by testing, download a copy, test it to find bugs and then report them to the bug list if there is no mark for such bug yet.
If you want to be a developer and write some code, download the source from CVS, compile it and try to run it. If everything is fine so far, go read the bug list and search for open bugs. Pick one and start wondering how to fix it. If you find a way to fix it, submit a patch somewhere where those are accepted with explanation of which bug it fixes, and ask someone to add your patch to the CVS.
You might find that hard, because most of the new developers won't ever get as far as submitting bug fixes. They might get the project compiled, but fixing bugs in a project which they are not familiar with, is hard. So if you really want to try, give yourself some time to learn the project. What is in each file how those files are connected to each other.
If you manage to fix a bug, you got some potential. Then just pick another one and start fixing that and little by little you will gain valuable experience and you will be able to fix harder and harder problems.
ps. I'm not an active member of this project, but I'm familiar with open source projects in general.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
[...] "If you manage to fix a bug, you got some potential. Then just pick another one and start fixing that and little by little you will gain valuable experience and you will be able to fix harder and harder problems."
and then if you still want to join project and the other developers (mainly Colin) think that you don't need supervision commiting fixes to cvs, you will be added to developers, if you'd still want to.
thanks Aggro for very complete description of the process ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Revision 1.140 - (view) (download) (as text) (annotate) - [select for diffs]
Wed Nov 17 13:59:04 2004 UTC (2 months, 2 weeks ago) by claplace
Branch: MAIN
CVS Tags: DEVCPP_4_9_9_1
Changes since 1.139: +3193 -3084 lines
Diff to previous 1.139
the same cvs tags are on all files in repository module V5.
so to checkout source of 4991, you need to specify tag DEVCPP_4_9_9_1 in your cvs client - in wincvs it's in update options->by revision/tag/branch. I believe in command line client it's -c option.
hope that helps
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
From what I've heard, Dev-C++ is supposed to be Open Source, so I get quite surprised to not find the source code availiable for download.
Dev-C++ is a very great program, but there is still a lot "potential for improving" in many areas. (By the way, how do I join the project?)
Can anyone please direct me to the source code for the latest release?
it's in cvs. it's hard not to find it for download
> By the way, how do I join the project?
What do you want to do? If you want to help by testing, download a copy, test it to find bugs and then report them to the bug list if there is no mark for such bug yet.
If you want to be a developer and write some code, download the source from CVS, compile it and try to run it. If everything is fine so far, go read the bug list and search for open bugs. Pick one and start wondering how to fix it. If you find a way to fix it, submit a patch somewhere where those are accepted with explanation of which bug it fixes, and ask someone to add your patch to the CVS.
You might find that hard, because most of the new developers won't ever get as far as submitting bug fixes. They might get the project compiled, but fixing bugs in a project which they are not familiar with, is hard. So if you really want to try, give yourself some time to learn the project. What is in each file how those files are connected to each other.
If you manage to fix a bug, you got some potential. Then just pick another one and start fixing that and little by little you will gain valuable experience and you will be able to fix harder and harder problems.
ps. I'm not an active member of this project, but I'm familiar with open source projects in general.
[...] "If you manage to fix a bug, you got some potential. Then just pick another one and start fixing that and little by little you will gain valuable experience and you will be able to fix harder and harder problems."
and then if you still want to join project and the other developers (mainly Colin) think that you don't need supervision commiting fixes to cvs, you will be added to developers, if you'd still want to.
thanks Aggro for very complete description of the process ;)
Is the current CVS the source for 4.9.9.1 or is it the development code for 4.9.9.2?
How can I get just the source code for 4.9.9.1?
Thanks.
-Tony
there are cvs tags for both.
Tony did you get my email?
to get the source of previous version you need to use cvs tags:
if you look at: http://cvs.sourceforge.net/viewcvs.py/dev-cpp/V5/devcpp.exe?rev=1.141&view=log
you'll see that each version of devcpp.exe in cvs has different cvs tags:
Revision 1.140 - (view) (download) (as text) (annotate) - [select for diffs]
Wed Nov 17 13:59:04 2004 UTC (2 months, 2 weeks ago) by claplace
Branch: MAIN
CVS Tags: DEVCPP_4_9_9_1
Changes since 1.139: +3193 -3084 lines
Diff to previous 1.139
the same cvs tags are on all files in repository module V5.
so to checkout source of 4991, you need to specify tag DEVCPP_4_9_9_1 in your cvs client - in wincvs it's in update options->by revision/tag/branch. I believe in command line client it's -c option.
hope that helps
Ok. I can see the 4.9.9.1 tag. Got to learn something new about CVS ;>)
-Tony
I discovered that Dev-C++ was written in Delphi, so I don't think I could improve on it anyway...
codeblocks is supposed to be alternative for dev-c++, and is written in c++ using wxwidgets