Just a minor correction.
As I understand it, you can download and use the Intel 11.0 Compiler for QNX Neutrino for QNX6.4 for *free* - you then 
have the *option* to purchase Intel's support plan for $299/year.
 
That's pretty much what it says here anyway:
http://www.intel.com/cd/software/products/asmo-na/eng/413548.htm
 
For free, it has to be worth a try... :-)
 
Regards
 
Dave
 
 
> <Flame_Bait>
> If only we could kick our addiction to open source compilers and debuggers so we could get good ones....
> </Flame_Bait>

You can already purchase the Intel Compiler.  But really, do you think QNX should be a compiler vendor.  And
just how many commercial compilers out there are not owned by, or at least tighly affiliated with, an OS company?

Cheers,

Colin

--
cburgess@qnx.com

_______________________________________________
General
http://community.qnx.com/sf/go/post23423

> Wow, great feedback, Kevin.
Well, I don't know about great, but I am rather opinionated ;)

> 
> Since you are using the IDE this can't be self-hosted.  Which host platform 
> are you using?

Windows

> A couple of questions/thoughts here...
> 
> The IDE talks to gdb via a pipe, with a text language called MI.  GDB then 
> talks to pdebug on the target
> via another protocol.  So there are already two levels of indirection there.
> 
> Add to that that each time you stop (whether it be a breakpoint, signal or 
> single-step), the ide will ask gdb
> about the current threads, the current breakpoints, the current shared libs, 
> the backtrace of each thread, and
> the values of registers/watch expressions, and there is a LOT of overhead.
> 
> Just for kicks, download cgdb, and run
> 
> cgdb -d ntox86-gdb myapp
> 
> and marvel at how fast things can be... I know it doesn't do any of the fancy 
> stuff mentioned above but
> you can see the effect that all that stuff is having.
> 
> I think it's likely that a lot of the overhead can be reduced by some 
> intelligent caching, but it's not there as
> yet.
> 
> WRT tcp/ip - you can debug an app over a serial line, is that what you mean?

I am using TCP/IP.  Thanks for the ip on cgdb, I'll check it out.

> 
> > <Flame_Bait>
> > If only we could kick our addiction to open source compilers and debuggers 
> so we could get good ones....
> > </Flame_Bait>
> 
> You can already purchase the Intel Compiler.  But really, do you think QNX 
> should be a compiler vendor.  And
> just how many commercial compilers out there are not owned by, or at least 
> tighly affiliated with, an OS company?

That is a good question, but no, I think you should focus on your main offering.  With that said, sometimes if the tools
 on which you rely to make a good product reduce your products viability, then maybe it wouldn't be a bad idea.

I don't think we are there yet, nor do I have any concrete reasons that would indicate this would be a good course of 
action.  But I do worry about community controlled things.  You don't have a lot of control over their direction.  If 
and when they start dictating what you product can do and can't do, then taking it in-house might deserve another look.


> 
> Cheers,
> 
> Colin
> 
> -- 
> cburgess@qnx.com

> -----Original Message-----
> From: Colin Burgess [mailto:community-noreply@qnx.com]
> Sent: March-03-09 9:18 PM
> To: general-ide
> Subject: Re: What do you want IDE to be?
>
> You can already purchase the Intel Compiler. 

Doesn't seems to be a version for Linux.  

> But really, do you think
> QNX should be a compiler vendor.  And
> just how many commercial compilers out there are not owned by, or at
> least tighly affiliated with, an OS company?
> 
> Cheers,
> 
> Colin
> 
> --
> cburgess@qnx.com
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post23423
> 

> Really great feedback! Thank you!
> I'd like just if you don't mind  to polish a bit your list.

Polish away, I wrote it hastily.

> Cannot agree more.  The question about builders (CDT and QNX) is one of 
> the top priorities for us and for CDT community. WE should do it better, 
> an I hope we'll do it before long.The issue is discussing actively right 
> now. That's why we would appreciate any ideas how to improve it.

Understood, you only have limited resources, but wanted to make mention of it.

> 
> > 2.  Managed Make projects need a way to export a makefile that can be built 
> on the command line w/o having to convert the project.   Maybe this is already
>  there, and I haven't seen it, but that would be nice.
> >
> >    
> I think in most cases you can do it now. Just select in tool chain 
> editor make builder instead of internal an build it in IDE at least once 
> to generate all infrastructure.

Cool...I'll give it a try...

> 
> > 3.  System Builder should create a build file that can be used directly with
>  mkifs so I can use the IDE, but then build with the command line.  Also, it 
> would be nice to transparently change between the command line and the system 
> builder.
> >    
> You can do it now, just use export feature of System Builder project.  
> About transparent change, this work ison the way, however is not 
> finished yet, but I belive (this is my private opinion) that brand new 
> component-oriented SB will be included into the next major release.

That's great!


> 
> > 4.  Should be able to be very specific as to where the IFS binaries get 
> linked.  mkifs tries to do too much.   Need.....more....control!  Maybe there 
> ways and tools to do this, but I just don't know about them?  I haven't had 
> time to ask specific questions..
> >    
> 
> Are you talking about Images combining? If yes, did you try this feature 
> in IDE or in command line? Anyway, it would be very nice to know more 
> details about your experience.

Sometimes, a processor's boot routine causes the reset vector to point to some ridiculous place in ROM/Flash to start 
executing.  For example, the MPC8349EA, if the reset word is configured such, the memory space becomes 0xFF800000 to 
0xFFFFFFFF and the reset vector starts at 0xFFF00100, that leaves a ton of space between the bottom of Flash and the 
reset vector.   If I want to put multiple images in between those locations for example, then I have to be careful that 
mkifs doesn't make something that will overwrite the reset vector.

Basically, I have a standalone IPL that is written, then I load the image separately.  I'd like to load two images for 
redundancy purposes, but I'm not sure how to have mkifs protect the reset vector area when it is creating a binary.

Also, I'd like the offset address to start at 0, instead of defaulting to 0xa000.  It allows me more flexibility to 
arrange code in flash to pack as much in there as possible.

> > 5.  Single key stroke building is tricky to use at best.  You have to have 
> the cursor in the right window and the right project selected on the Projects 
> view.  It isn't clear how to make this work well.  It would be nice to have an
>  'active' project type concept so that when you select build, the active 
> project and all its dependencies are built.  This way I wouldn't have to care 
> if I had the correct window/project selected.
> >    
>   Is it about container project? Could you elaborate this point?

No, not a container project.  Say for example you have a workspace with 10 projects.  Most are libraries, but you have 
two projects that are binaries (with main()).

The binary projects need to reference some of the library projects.  Lets say you are working on some library code and 
want to test.  You have to...