What IDE DID you use?

[gnirts]

Originally Posted by Astronouth7303

Maybe next year, I can get CDs in all the kits. (I'll need lots of help!)

FIRSTclipse doesn't need 1400 CDs, but you do need a click-n-go installer available for download from SF that just plain works. I spent the better part of a day after school getting it to work on my machine, the trick ended up being specifing the library files w/o spaces (eg. C:\EXAMPL~1\E-PATH~1\IN-OLD-F~1\ORMAT~1\FRC_AL~1.LIB). Eclipse and the MCC18 tools also didn't play well at first with Subversion (Clean->Build All deleted some .svn directories and corrupted a repo I had going when I tried to commit the .hex files, luckily I was only 3 revs in from the default code). There were other issues as well, lots of tweaking paths-especially under Linker Information-and fiddling with MinGW make (which does work). It's just not as convienent as MPLAB.

However, I haven't run MPLAB since April of last year. Refactoring support, a quick diff viewer, and autocomplete are addictive, as is Ctrl+F3.

Other than that, I usually prototype with Dev-C++ when doing quirky C things like function pointers and Zend Studio 5.2 when just playing with program logic.

Robinson Levin

[taylort]

We used Code::Blocks, as well as just simple text-editing stuff.

[JonathanLKS]

Originally Posted by taylort

We used Code::Blocks, as well as just simple text-editing stuff.

We also used Code::Blocks

[Shinigami2057]

We used an odd combination of KScope (GREAT program), emacs, and bluefish in combination with a Makefile. It worked very well, and we also utilized a subversion repository which really helped (revision 32 as of ship, we would've been at ~50 or more if we started it right at kickoff).

[Billfred]

This is going to shock a few people, but none of the above. We have yet to push the program button on the 2007 RC; it's all running on default code. Some of that might change come Palmetto; for the amount of stuff we're doing to the code (read: not much), I expect to use MPLAB.

[WaterFreak]

I used SlickEdit for all of my code writing. It has an interface I am used to (use it all the time at work) and some way cool features, most powerful of which is a project wide search feature.

It does also NOT have some of the goofy window placement issues I had with MPLAB.

Naturally, still use MPLAB to compile the code.

[bear24rw]

For those of you who used Code::Blocks, did you compile directly with the mcc compiler? or did you just use it to edit code..

[Astronouth7303]

Originally Posted by gnirts

FIRSTclipse doesn't need 1400 CDs, but you do need a click-n-go installer available for download from SF that just plain works. I spent the better part of a day after school getting it to work on my machine, the trick ended up being specifing the library files w/o spaces (eg. C:\EXAMPL~1\E-PATH~1\IN-OLD-F~1\ORMAT~1\FRC_AL~1.LIB). Eclipse and the MCC18 tools also didn't play well at first with Subversion (Clean->Build All deleted some .svn directories and corrupted a repo I had going when I tried to commit the .hex files, luckily I was only 3 revs in from the default code). There were other issues as well, lots of tweaking paths-especially under Linker Information-and fiddling with MinGW make (which does work). It's just not as convienent as MPLAB.

However, I haven't run MPLAB since April of last year. [color=DarkOrange]Refactoring support, a quick diff viewer, and autocomplete are addictive, as is Ctrl+F3.

Other than that, I usually prototype with Dev-C++ when doing quirky C things like function pointers and Zend Studio 5.2 when just playing with program logic.

Robinson Levin

Yeah. Part of the problem is that GNU Make and the Makefile generator fights me. You have to do things like double quote (""C:\mcc18\lib"") to get it to work.

The other problem is that I don't think I can distribute MCC18 with it.

The only time MinGW fails is when you pass flags like "/w", which I think is required for MPASM.

I'll be the first to admit. FIRSTclipse has a long way to go. MCC18 and the CDT don't really mesh well. The error parser just fails miserably when using Wine.

All I can say is to help. Contribute code. Test new versions. Make packages. All I know is I can't do it all myself.