Battle Stations!
Pages: 12
Post your battle...er I mean Development Environment. Do you use an IDE? Or is it a comline toolset and text editor combo. What text editor do you use if so?Also, do you use one or more monitors when developing. If more how many? Do you use any documenting software or anything like subversion. What OS do you favor in development. And finally what compiler set do you use?
I'm asking all this as a small survey, I'm going to do some statistical analysis on the data and figure out statistically what is the favored environment for programming. Partly because I want to a bit of a change from my normal virtual habitat and I'm fishing for what might be best...but mostly because I'm bored.
I'll start:
IDE or Text Editor + CLI compiler: Text Editor + CLI compiler
Toolkit/compiler: GCC 4.4.3
Text Editor: gedit
Debugger: GDB 7.1
Number of monitors: 3
Documenting or version standardizing software: None
OS: Slackware64 with 32 bit libraries and headers installed as well.
I'm asking all this as a small survey, I'm going to do some statistical analysis on the data and figure out statistically what is the favored environment for programming. Partly because I want to a bit of a change from my normal virtual habitat and I'm fishing for what might be best...but mostly because I'm bored.
I'll start:
IDE or Text Editor + CLI compiler: Text Editor + CLI compiler
Toolkit/compiler: GCC 4.4.3
Text Editor: gedit
Debugger: GDB 7.1
Number of monitors: 3
Documenting or version standardizing software: None
OS: Slackware64 with 32 bit libraries and headers installed as well.
Last edited on
I use mainly the IDE but sometimes I use gedit or cat
IDE: Code::Blocks 10.05
Compiler: GCC 4.5.0
Debugger: GDB 7.1
Monitors: 1
OS: Ubuntu 10.04
IDE: Code::Blocks 10.05
Compiler: GCC 4.5.0
Debugger: GDB 7.1
Monitors: 1
OS: Ubuntu 10.04
@ Bazzy:
Hey mate, how did you install code blocks 10.05?
I am very challenged with computers, so I would love to see a simple (point and click if possible, although I doubt it) instructions designed for dummies without any special computer skills.
Where can one find such? I once downloaded some svn repository, but ./configure, make, and make install were beyond the default puny abilities of my ubuntu (something went wrong...).
Btw I use code blocks 8.02 (the default you can point-and-click install on Ubuntu).
Hey mate, how did you install code blocks 10.05?
I am very challenged with computers, so I would love to see a simple (point and click if possible, although I doubt it) instructions designed for dummies without any special computer skills.
Where can one find such? I once downloaded some svn repository, but ./configure, make, and make install were beyond the default puny abilities of my ubuntu (something went wrong...).
Btw I use code blocks 8.02 (the default you can point-and-click install on Ubuntu).
@tition:
Code::Blocks 10.05 Can be installed through Ubuntu Software Center in Ubuntu 10.04
what edition of ubuntu are you using?
Code::Blocks 10.05 Can be installed through Ubuntu Software Center in Ubuntu 10.04
what edition of ubuntu are you using?
OS: Windows XP SP3/Debian stable
IDE: VC++ 9.0/Eclipse
Compiler: (VC++ 9.0/ICC 11.0/MinGW 4.4/MinGW 3.4.5 [for single file programs or quick tests only])/GCC.
Debugger: Visual Studio debugger/(Eclipse+gdb/Valgrind)
SCM: (Subversion/Git)
Text editor: Notepad++/(Kwrite/wine npp)
Valgrind is the best thing since the subroutine.
IDE: VC++ 9.0/Eclipse
Compiler: (VC++ 9.0/ICC 11.0/MinGW 4.4/MinGW 3.4.5 [for single file programs or quick tests only])/GCC.
Debugger: Visual Studio debugger/(Eclipse+gdb/Valgrind)
SCM: (Subversion/Git)
Text editor: Notepad++/(Kwrite/wine npp)
Valgrind is the best thing since the subroutine.
is there a *nix port of Valgrind? or is it windows only?
EDIT: nevermind, gonna google, it's been a long day ^^;;
EDIT: nevermind, gonna google, it's been a long day ^^;;
Last edited on
Eclipse Galileo with CDT
GNU make
GCC 4.4.4
Eclipse, DDD-3.3.12 (w/GDB 7.1), Valgrind and GCC's mudflap
Subversion and Git
Doxygen
Boost Test
gedit & vim
2x20" 1600x1200 IPS LCDs
GNU make
GCC 4.4.4
Eclipse, DDD-3.3.12 (w/GDB 7.1), Valgrind and GCC's mudflap
Subversion and Git
Doxygen
Boost Test
gedit & vim
2x20" 1600x1200 IPS LCDs
| tition wrote: |
|---|
| Hey mate, how did you install code blocks 10.05? I am very challenged with computers, so I would love to see a simple (point and click if possible, although I doubt it) instructions designed for dummies without any special computer skills. Where can one find such? I once downloaded some svn repository, but ./configure, make, and make install were beyond the default puny abilities of my ubuntu (something went wrong...). |
its easiest to install code blocks on windows cos you can download the MinGw version which comes with everything you need and all you need to do is install. however for ubuntu you have to set up a compiler yourself.
| however for ubuntu you have to set up a compiler yourself. |
@Bazzy
I gave it a try once again. An hour of lost time with 0 success (codeblocks_10.05-1_i386 claimed codeblocks-common_10.05-1_all was not up-to-date, although the previous two clicks of the mouse I just installed the latter package).
This is beyond my linux abilities... I will postpone my attempts to install an up-to-date code::blocks version to a later time, when either my linux abilities have increased, or the installation procedure has become more sane.
I gave it a try once again. An hour of lost time with 0 success (codeblocks_10.05-1_i386 claimed codeblocks-common_10.05-1_all was not up-to-date, although the previous two clicks of the mouse I just installed the latter package).
This is beyond my linux abilities... I will postpone my attempts to install an up-to-date code::blocks version to a later time, when either my linux abilities have increased, or the installation procedure has become more sane.
Can't you just do
I installed in on Arch and all I did was
What? That's ridiculous, no you don't.
Again, all I had to do was type
# apt-get install codeblocks ?I installed in on Arch and all I did was
# pacman -S codeblocks ... It was easy.| its easiest to install code blocks on windows cos you can download the MinGw version which comes with everything you need and all you need to do is install. however for ubuntu you have to set up a compiler yourself. |
What? That's ridiculous, no you don't.
Again, all I had to do was type
# pacman -S codeblocks and wait a minute or two for it to download and extract the binaries, and put them in the appropriate directories. All of it was done automatically for me.
The current version of Ubuntu is 10.04, Code::Blocks 10.05.
So C::B came one month after the release of Ubuntu. For this reason it can't be in the repositories
So C::B came one month after the release of Ubuntu. For this reason it can't be in the repositories
The complaint above that using apt-get to install C::B didn't work properly under Ubuntu, due to some dependency version conflicts...
pacman is for Arch Linux. Just because your system works perfectly doesn't mean everyone else's system will work perfectly...
pacman is for Arch Linux. Just because your system works perfectly doesn't mean everyone else's system will work perfectly...
apt-get codeblocks works on Ubuntu but provides an older version, it's the source that can't be compiled with default libraries
@Duoas,
I know; I'm just saying that it worked on Arch. I don't see why it doesn't work on Ubuntu. I also think it's ironic you would say that "Arch Linux [...] works perfectly" because it's known for being relatively unstable. That's a side effect of getting all your software from upstream.
@Bazzy,
Why can't they just add it to the repo?
I know; I'm just saying that it worked on Arch. I don't see why it doesn't work on Ubuntu. I also think it's ironic you would say that "Arch Linux [...] works perfectly" because it's known for being relatively unstable. That's a side effect of getting all your software from upstream.
@Bazzy,
Why can't they just add it to the repo?
Ubuntu releases are s...l...o...w... (or rather, having the latest software in the releases is...)
And don't confuse (logical) processes.
Arch Linux may be a piece of crap. That doesn't nullify the fact that you were able to make it do the Right Thing. That is one argument.
Ubuntu's success or failure has nothing to do with Arch Linux's success or failure. That's another argument.
That's all I said.
And don't confuse (logical) processes.
Arch Linux may be a piece of crap. That doesn't nullify the fact that you were able to make it do the Right Thing. That is one argument.
Ubuntu's success or failure has nothing to do with Arch Linux's success or failure. That's another argument.
That's all I said.
| Duoas wrote: |
|---|
| Ubuntu releases are s...l...o...w... (or rather, having the latest software in the releases is...) |
Fair enough. This is all I wwanted to know.
| And don't confuse (logical) processes. Arch Linux may be a piece of crap. That doesn't nullify the fact that you were able to make it do the Right Thing. That is one argument. Ubuntu's success or failure has nothing to do with Arch Linux's success or failure. That's another argument. That's all I said. |
I didn't say Arch Linux was a piece of crap. It's just known for having "bleeding edge" upstream software that's not always completely stable. That was not an argument, it was simply an observation. I use it because I like having up-to-date software all the time.
Pages: 12