Wascana is Eclipse Based Standalone C++ IDE for MS Windows
Wascana Desktop Developer is a completely standalone, Eclipse-based C++ development environment for the Windows platform which packages everything that is needed for developing applications using the C++ language. Download the installer, go through the installation wizard and you have a complete C++ IDE ready to go; unlike EasyEclipse for C++, no additional software or any further configuration is needed. It is based on the popular Eclipse platform and uses the CDT plugin and the MinGW compiler tools to provide the necessary functionality. Called CDT for Windows earlier, it is now renamed to Wascana Desktop Developer to avoid any trademark issues. The latest version, Wascana 0.9.3, was released a few days ago and it comes with the following components integrated into it:
- Rich development environment of the Eclipse platform.
- Eclipse CDT Plugin.
- MinGW and MSYS C++ development tools.
- wxWidgets and SDL C++ libraries.
Wascana is currently under active development mode and I am guessing that the version ready to be used by a typical user would be released as Wascana 1.0. Those who are interested can download and try it out right away, there is nothing scary in the 0.9.3 version and it is fully functional and extremely stable. What more is planned for the future? From Doug’s blog(Wascana’s creator), it looks like:
- Integrated support for Boost.
- More C++ libraries; like, perhaps, the game development library Ogre 3D.
- Support for Microsoft compiler and debugger(MinGW and Cygwin are already there).
- .NET support and a GUI Builder.
- Support for GNU/Linux and Mac OS X platforms.
So if you see the above list you realise that it is not going to be a thin layer of packaging to just integrate the Eclipse and MinGW tools together, but rather going to be a complete, rich development environment for C++ developers, which in future might become, according to Wascana’s creator, as good an IDE as Microsoft Visual C++ for Windows, perhaps with full community involvement. Except for (5) above, I am excited about the future roadmap of Wascana.
Things I personally would like to see in the future versions of Wascana:
- Good support for Unit testing. CppUnit, CxxTest, almost anything will do.
- Some of the popular C++ libraries: Boost, ACE, Loki etc.
- More C++ related plugins like Doxygen. [Plugins to enable profiling, static analysis and logging support would be good too.]
- SCons-Builder! I know that every C++ programmer has his own favourite build tool(bjam, cmake, nmake, etc) but SCons is too good to be ignored I believe.
- Test support for CVS as well as Subversion plugins. Not high priority.
Much of the above stuff should actually be better supported by the core Eclipse C++ project(Eclipse + CDT) but I will not be the one complaining if they are instead well supported by the other Eclipse based C++ IDEs like Wascana, EasyEclipse etc :) Also, I don’t expect all of the above to be an integral part of a future Wascana release(except Boost and unit testing libraries); if they are tested thoroughly enough to make sure that they work well with every new Wascana release, it would work for me. This lack of documentation regarding which versions of plugins work with which versions of Eclipse has been the biggest gripe for me.
[I will make a proper dream-list of the features I would like to see in what could be my perfect C++ IDE and will post it in a separate blog entry.]
Getting Started with Wascana Desktop Developer 0.9.3
To try Wascana out, download the latest version from Wascana’s sourceforge.net page. Go through the installation wizard and when finished, run the application from the Start menu(or use the Desktop shortcut).
From inside Wascana, create a new C++ project(File -> C++ Project; Makefile Project -> Hello World C++ Project -> MinGW GCC) and try to build it.
Project -> Build Project will build it. Run -> Run as Local C/C++ Application will create the run configuration and then will run the application(Ctrl-F11 will run it from the next time). (Edit first if you frown like me at the default generated code. When starting a real C++ project though, you can either create an empty C++ project or import an existing project using File -> Import…).
More Options in Wascana
As you can see, we have created an example C++ project, built it and run it in Wascana Desktop Developer without having to download and install MinGW/MSYS or any other software and without having to bother setting up the PATH variable. Of course, if you want to use your own version of MinGW toolchain, you can override the packaged MinGW version by preceding/replacing path to Wascana’s MinGW/MSYS with that of yours in Wascana preferences(Project -> Properties):
Need to run some tool from the command line outside of Wascana? Run MSYS command line tool that comes with Wasacana(Start -> Wascana -> Wascana MSYS or Desktop shortcut):
Last Words
Wascana is a great idea in its current form and has the potential to become one of the best C++ development environments in the future. I do hope that (1) the support for Windows application development in the future versions of Wascana won’t come in the way of pure C++ development(where GUI or Microsoft library support is not needed) and (2) even if Doug offers a commercial version of it in the future, a community version is always made available. Keep a watch on the blog of Doug Schaefer, Wascana’s creator and an Eclipse CDT developer, for more information.
Thanks for this kind post :). I’ll definitely take your suggestions. I agree with you on the Linux/Mac front. The idea was to give the identical environment for people on those platforms but the Linux distros are doing a good job of getting the CDT there and I don’t have a Mac to even see what needs to be done there. Windows is the platform that needs the most attention right now and we should probably refocus just on that.
Beyond libraries, I see Unit Test as being a critical add on. We do have an old CPPUnit integration but I’m not sure it works now or whether other packages are now better. There are a few people in the CDT community poking at Doxygen too. And I’ve been bugged about Scons integration since the early days of the CDT :).
Thanks again! Doug.
QuoteComment by Doug Schaefer — September 14, 2007 @ 8:06 pm
Which g++ version is included in Wascana? 3.4.5 or a later version?
QuoteComment by Bob — September 15, 2007 @ 8:28 pm
It’s still at 3.4.5. There was a light of hope for moving to 4.2.1, but Danny Smith, the gcc maintainer for mingw has stepped down. Hopefully someone else will pick it up. What I saw of it, 4.2 rocks with some awesome global optimizations. It made me thing that I wouldn’t need to integrate with the Microsoft compiler. But there were bugs in it.
gdb still has issues with the Windows stack, though, especially when you suspend in the middle of a win32 call. That’s another issue that will need to be addressed. I’m not sure anyone is looking at that either.
QuoteComment by Doug Schaefer — September 15, 2007 @ 8:57 pm
I am glad to read that you are looking to refocus on the Windows version as of now.
I have used plugins for CppUnit and CxxTest in Eclipse: I hate CppUnit’s graphical QtTestRunner but it is adequate if its console TestRunner is acceptable. CxxTest integrates very well with Eclipse GUI but I couldn’t run it with MinGW toolchain yet(ran well with Eclipse/Cygwin and outside of Eclipse).
The Scons-Builder plugin for Eclipse lacks documentation, is far from perfect, but it is functional to the extent that I rarely have to leave Eclipse and go to the command-line to use SCons. I love the integration of Eclox/Doxygen, AnyEdit plugins in EasyEclipse.
Finally, I must say that it’s heartening to see such positive response from you to the users’ feedback :)
QuoteComment by tabrez — September 15, 2007 @ 9:28 pm
Please integrate the ACE library with Wascana. Thanks!
QuoteComment by Ryan — September 30, 2007 @ 1:56 am
[...] with Eclipse Europa, CDT plugin, MinGW toolchain (among other things) all integrated together. Read my post about the Wascana IDE for more [...]
QuotePingback by Build C++ Programs With SCons in Eclipse Using SConsBuilder Plugin(MS Windows) — October 24, 2007 @ 9:15 pm