aMule Forum

English => Offtopic Section (Nonsense inside) => Small talk => Topic started by: Mr Faber on March 18, 2005, 07:27:46 PM

Title: which dev tools are recommendable
Post by: Mr Faber on March 18, 2005, 07:27:46 PM
Which dev tools are recommendable/which are you using for developing aMule?
I am not an developer but I have some very basic C++ knowledge and write some little private patches for eMule. Now I want to do the same with aMule and maybe extend my knowledge :)
For eMule I uses Notepad++ or the editor of VS 7 and winmerge.

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 18, 2005, 07:41:26 PM
All you need is an editor and the various GNU tools (gcc/gdb/make/etc). However, other tools can also be useful, such as valgrind, oprofile, etc.
Title: Re: which dev tools are recommendable
Post by: Mr Faber on March 18, 2005, 07:51:32 PM
I know that but which editor do you use? I want to use editors/additives that are well tested and optimal for programming. :)
Since I have Gentoo the GNU tools are already there :D

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 18, 2005, 08:31:40 PM
Ok, that's hard to give a good answer to. There are quite a lot of editors, but emacs/vim seems to be the most common recommendations. Or if you want a full development environment, then something like kdevelop or eclipse. I can only really recommend that you try out some different editors and see what works for you.

I personally use gVim.
Title: Re: which dev tools are recommendable
Post by: Mr Faber on March 18, 2005, 08:58:58 PM
Thats good because I have only some experience with vim even if very basic too but I have some :)
It is such a big change-over to come from windows "drag and drop" and "copy and paste" to an editor like vim but it has it advantages too.

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: lfroen on March 18, 2005, 09:09:42 PM
Eclipse have match better cvs support that kdevelop, but kdevelop integrates with gdb better and consumes less memory
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 18, 2005, 09:12:44 PM
For CVS I'd recommend Cervisia.
Title: Re: which dev tools are recommendable
Post by: Mr Faber on March 18, 2005, 09:26:30 PM
Thanks! :baby: I will check them out.

[EDIT]Kdevelop looks very good :) A little bit like VS 7 :D
Does KDevelop have some problems with the GTK-Interface of aMule? Has it some influence on compiled aMule like integrating of qt libs?
[/EDIT]

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 18, 2005, 10:46:28 PM
There shouln't be any problems as far as I can see.
Title: Re: which dev tools are recommendable
Post by: phoenix on March 19, 2005, 12:10:46 AM
Real programmers use console tools :P

Ok, I admit it, I use gvim :D But other than that, all is console: gdb, grep, find, less, make, etc.
Title: Re: which dev tools are recommendable
Post by: Kry on March 19, 2005, 03:25:28 AM
I use anjuta.
Title: Re: which dev tools are recommendable
Post by: Mr Faber on March 19, 2005, 01:16:53 PM
Is there any amule project file for kdevelop?

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 19, 2005, 01:38:29 PM
Afraid not.
Title: Re: which dev tools are recommendable
Post by: phoenix on March 19, 2005, 03:14:50 PM
Quote
Originally posted by Mr Faber
Is there any amule project file for kdevelop?

cu
Mr Faber
What do you mean? Just create one. You just have to untar the files and choose an automake based build. Set the configure options and you're done.

My only problem with kdevelop is that it is not working here with gdb, so it's supposed best feature is useless. But it is nice to grep without going to the prompt, also CVS support is honest.
Title: Re: which dev tools are recommendable
Post by: GonoszTopi on March 19, 2005, 04:57:58 PM
I use cvs for CVS support and mc -> F4 for editing, and all these are nicely surrounded by an xterm  8)

Really, I use the editor that lies closest to my hand. For larger things I prefer emacs, it can take care of the coding guidelines instead of me.  ;)

Now, all the above is just fun. The truth is, as you might have noticed it from my avatar, I edit the binary, then run it trough a tool that creates C++ code from it.
(I swear I wrote progams in binary - well, actually in hex)
Title: Re: which dev tools are recommendable
Post by: Mr Faber on March 23, 2005, 11:05:45 PM
@GonoszTopi
This is really strange. :)
How do you learned it and how do you can combine it? Were you a computer in your last life? ;)

cu
Mr Faber
Title: Re: which dev tools are recommendable
Post by: Xaignar on March 24, 2005, 12:01:46 AM
It's not really that hard (provided that you work with a sane architecture), but it isn't much fun either. It's mostly just a lot of looking up in tables of opcodes. :p
Title: Re: which dev tools are recommendable
Post by: phoenix on March 24, 2005, 04:08:05 AM
Yeah, after some time you can actually read and write the hex codes. Thanks god I no longer do that. Since Z80/8085 times :D

The nice thing is that you could get some undocumented instructions to work.
Title: Re: which dev tools are recommendable
Post by: Ateo on June 23, 2005, 08:12:40 AM
Oh my Lard. I was considering tackling learning C++ but you guys just scared the piss out of me with all this geek talk.
Title: Re: which dev tools are recommendable
Post by: lfroen on June 23, 2005, 05:04:23 PM
Xaignar: it becomes hard when you have more registers (all hail SPARC). Intel's opcodes are quite easy to deal with; 68xxxx are ok, but written backwords :)