Why wait for the next release …

OK … so I promise that this will be my last post about foundry27for a while and I’ll get back to talking about QNX technology.  But I couldn’t help myself, I needed to put out one more plug for some of the QNX Neutrino software that is being made more accessible to developers.

This time it is the availability of the IDE, also commonly known as QNX Momentics, although that statement will get me in trouble since QNX Momentics is more than just the IDE, but it is the complete assembly of a development environment for QNX Neutrino … but I digress.

The IDE is not part of the current roadmap for source publishing, but the QNX tools development team is shifting to performing its development work more transparently.  To that end there are two community projects, the Core Development Tools project and the the Integrated Development Environment (IDE) project.  From the Core Development Tools project you can get the bleeding edge versions of the GNU toolchain as they are developed … which is interesting, but most commercial projects currently under development aren’t likely to switch to a non-released (by QNX) compiler for their production work.   The IDE also offers bleeding edge integration build downloads and since the IDE pretty much sits on top of any core tool or runtime components, it can be updated with far less risk to a production development environment.   While I hate to compare the IDE to an editor, updating your IDE is like updating your editor:  In theory new features and functionality should only make you more productive!

The IDE team is tracking what significant new and noteworthy features are being added to each of the integration builds so you can get an immediate idea of what areas you might want to explore.  A more visual page is alsotracking the general IDE 4.5 features that you might also want to take a look at.  There is a lot of goodness in these downloads, ranging from the source navigation and usability improvements in the C/C++ development environment to the brand new Application Profiler functionality and a range of smaller, but equally rewarding, fixes and enhancements.

The other benefit to trying it out early is that the IDE team is actively looking for feedback and there is still time in the schedule before the next major release … codenamed Athens … to respond to feedback and feature requests.

Of course I’m a bit biased since I’ve had a hand in putting some of the new IDE features in, but I’ve switched for my C/C++ development and I’m not going back!



6 comments so far

  1. Mario on

    Hey Thomas,

    I’ve noticed that in all the wiki pages about downloading/install/building various component ( OS/Network ) there is never any instruction about doing it from the IDE. For example how would I build the whole OS from the IDE?

  2. sendreceivereply on

    The great thing about the IDE is that you don’t actually have to change anything significant about your build system or the way you work in order to use it.

    The bad thing is that there are many different ways to approach it, which may or may not fit the way you work.

    Here is one proposal:
    – Get the source onto you computer
    * Use the command line svn client to do this
    * Use the IDE to do this with one of the SVN eclipse plugings (I suggest subclipse from tigris.org)

    – Get the source into your workspace
    * Create a C/C++ Standard Make project and map it on top of where you checked the source out from.
    If checked out from the IDE, then you already have it.

    – Create the qconf-override.mk file … the same directions apply as the command line build

    – Set the QCONF_OVERRIDE environment variable in the project properties to be set any time that a command runs. You don’t need this if you have a global environment variable that is picked up when you run the IDE.

    – Use the Make Targets to create an ‘hinstall’ and an ‘install’ target the same as the command line build.

    Now build it by invoking the appropriate make target(s)

    IDE integration is not as difficult as it seems, it is just about finding the “IDE way” of doing all the things that you would do from the command line.

  3. sendreceivereply on

    Just as a follow up, we do have some IDE directions and a workspace that we hope to put up on one of the pages at some point … perhaps sooner rather than later.

  4. Mario on

    Subclipse make Eclipse (Tau) crash. Never easy isn’t it ;-)

  5. Thomas Fletcher on

    Really? I use subclipse and Tau on a regular (once an hour) basis. Of course you and I had some discussion back and forth on getting it installed, so perhaps there is some dependency bit that got messed up during your installation or that is satisfied in mine since I have the Java development plugins installed as well.

    In the meantime:
    * Just checkout the source using the command line svn tools
    * Follow the same instructions.

    Remember, the IDE should bend to your will, not the other way around, and with few exceptions it does just that.

  6. Mario on

    Once you get the IDE to recognize the project, how do you build say pidin or any other library or util. Do I have to build make file target for each of them.

    But then what if redo this whole cycle in 2 months with a fresh check out I have to build the make file target again?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: