We don't really remove any linux support. You can create for example Managed C project and select linux toolchain 
instead of Qnx toolchain. I
t would build a linux executable.


Ken Schumm wrote:
> I've been using the QNX 6.4.0 development on Kubuntu and have really been enjoying the stability and rich utility set 
compared to windows.
> 
> I'd like to also develop some linux binaries that will talk to our embedded QNX devices from linux. Of course the QNX 
development tools, as installed, don't allow the creation of linux binaries.
> 
> Can anyone recommend a good approach for this?
> 
> If another eclipse toolset was installed for linux code development would it conflict with the QNX toolset?
> 
> Or, are there simple ways to extend the QNX tools to develop linux binaries?
> 
> I haven't explored how to extend eclipse in any detail and am trying to avoid screwing up my primary QNX development 
environment.
> 
> TIA
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post27139
> 

Ken Schumm wrote:
> I've been using the QNX 6.4.0 development on Kubuntu and have really been enjoying the stability and rich utility set 
compared to windows.
> 
> I'd like to also develop some linux binaries that will talk to our embedded QNX devices from linux. Of course the QNX 
development tools, as installed, don't allow the creation of linux binaries.

You should be able to use regular C project (not QNX, just C 
project). I am not familiar with Kubuntu, but linux 
distributions usually include toolchain; if not, I am sure 
there is an easy way to install it.

---
Aleksandar

I use Ubuntu.  When self hosting our build system is generating some custom tools use later in the build process.  That 
was a major pain to move over Windows.  With Ubuntu for these tools I simply changed qcc for gcc and that was it!  Had I
 known this I don't think we would have spent all this time moving over Windows, but given QNX constant change of 
direction ( for example drop for Solaris ) sticking with the most "standard" stuff is probably safer.

In fact I wouldn't be surprised if in a couple of years we switch to Linux all together now that self hosted for 
development is going the way of the dodo.

> -----Original Message-----
> From: Ken Schumm [mailto:community-noreply@qnx.com]
> Sent: April-15-09 4:16 PM
> To: general-toolchain
> Subject: Eclipse, QNX and Kubuntu
> 
> I've been using the QNX 6.4.0 development on Kubuntu and have really
> been enjoying the stability and rich utility set compared to windows.
> 
> I'd like to also develop some linux binaries that will talk to our
> embedded QNX devices from linux. Of course the QNX development tools,
> as installed, don't allow the creation of linux binaries.
> 
> Can anyone recommend a good approach for this?
> 
> If another eclipse toolset was installed for linux code development
> would it conflict with the QNX toolset?
> 
> Or, are there simple ways to extend the QNX tools to develop linux
> binaries?
> 
> I haven't explored how to extend eclipse in any detail and am trying to
> avoid screwing up my primary QNX development environment.
> 
> TIA
> 
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post27139
> 

You can also monitor this project: 
http://wiki.eclipse.org/images/f/f1/ExtendedIDE_C_Linux_20090127.pdf
Though I don't know the level of its maturity.

On 15/04/2009 4:15 PM, Ken Schumm wrote:
> I've been using the QNX 6.4.0 development on Kubuntu and have really been enjoying the stability and rich utility set 
compared to windows.
>
> I'd like to also develop some linux binaries that will talk to our embedded QNX devices from linux. Of course the QNX 
development tools, as installed, don't allow the creation of linux binaries.
>
> Can anyone recommend a good approach for this?
>
> If another eclipse toolset was installed for linux code development would it conflict with the QNX toolset?
>
> Or, are there simple ways to extend the QNX tools to develop linux binaries?
>
> I haven't explored how to extend eclipse in any detail and am trying to avoid screwing up my primary QNX development 
environment.
>
> TIA
>
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post27139
>
>