Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
IDE/Discussion/General/C Project vs. QNX C Proj/List of Posts
Forum Topic - C Project vs. QNX C Proj: (4 Items)
   
Update
Chris Foran
09/13/2008 3:03 PM
post13372
C Project vs. QNX C Proj   
Could somebody please provide a quick summary of C Projects vs. QNX projects in 4.5, and what the anticipated different 
usages would be?

Why is the Standard make project gone in 4.5?  I assume that the 'C Project' is it's replacement?

If a developer using the IDE wanted to share their project with a developer who preferred command line tools, would one 
project be preferable to the other?  

Thanks,

--Chris Foran
Alex Chapiro
09/13/2008 9:22 PM
post13377
Re: C Project vs. QNX C Proj   
Gossips about regular make project passing away could not be confirmed 
by any reliable source :-) You still can create it using  C or C++ 
wizard. Having on your screen the first wizard panel, select in the left 
tree Makefile project and Empty project. THen on the right panel select 
QNX QCC toolchain and press finish. You can also press  Next instead of 
Finish and in the following panel press button Advanced Setting, then 
select C/C++ Build and pre-set build target properties and and other 
parameters. This is almost the same as Set QNX Environment action in 
oprevious release. It can be also done later via properties dialog.
Anyway finally you'll get new empty regular make project. Unfortunately, 
we were very limited now by  CDT 4 as well as in tyme and work force, so 
I'm not very happy with   this solution. However, I'm sure that wewill 
improve usability dramaticallyt in the next release.
I know for sure that the question about MBS and QNX builders whas been 
already addressed in this forum by Elena, but I was unlucky trying to 
find this thread. Briefly, MBS and QNXp projects are both managed 
projects. QNX project as you can see from its name is QNX oriented  and 
based on recoursive make files (which means it to be very useful for 
multi-platform defelopment). I would mention two features of MBS build 
system: First,  it's  its  flexibility: it can be used for various tool 
chains (QNX supports only qcc and intel) if appropriate toolchain 
definition added to xml  descripting file). Second, beside make-based 
builder MBS has its own internal builder which in perspective (not now, 
don't be afraid) should completely replace make builder. However, in my 
opinion (and not only my)  it is too early to do it

Don't hesitate to ask more if it is "too brief" for you.

Regards,

Alex
Chris Foran wrote:
> Could somebody please provide a quick summary of C Projects vs. QNX projects in 4.5, and what the anticipated 
different usages would be?
>
> Why is the Standard make project gone in 4.5?  I assume that the 'C Project' is it's replacement?
>
> If a developer using the IDE wanted to share their project with a developer who preferred command line tools, would 
one project be preferable to the other?
>
> Thanks,
>
> --Chris Foran
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post13372
>
>
Chris Foran
09/16/2008 6:37 AM
post13458
Re: C Project vs. QNX C Proj   
Thanks for the reply Alex.

I am attempting to follow your suggested steps to create the equivalent of a standard make project, and I'm having 
trouble.

I create a new C project-->Makefile project-->empty project-->finish

Then I simply pasted a helloworld.c and a Makefile into the project.  Then, right click-->build project.

What I'm getting is below.  What is pch_support?  Why is it trying to build with coverage?  I'm just using defaults, and
 my makefile doesn't have any coverage options.

Thanks

**** Build of configuration Generic/QNX for project t4 ****

make all 
qcc -g -Vgcc_ntox86 -w9  -g -Vgcc_ntox86  hello.c   -o hello
C:\QNX640\host\win32\x86\usr\bin\ntox86-ld: %(ftest-coverage:-lgcov): No such file: No such file or directory
cc: ignoring unknown option 'pch_support'
cc: ignoring unknown option 'pch_support'
cc: C:/QNX640/host/win32/x86/usr/bin/ntox86-ld caught signal 1
make: *** [hello] Error 1
Ryan Mansfield(deleted)
09/16/2008 8:12 AM
post13461
Re: C Project vs. QNX C Proj   
Chris Foran wrote:
> Thanks for the reply Alex.
> 
> I am attempting to follow your suggested steps to create the equivalent of a standard make project, and I'm having 
trouble.
> 
> I create a new C project-->Makefile project-->empty project-->finish
> 
> Then I simply pasted a helloworld.c and a Makefile into the project.  Then, right click-->build project.
> 
> What I'm getting is below.  What is pch_support?  Why is it trying to build with coverage?  I'm just using defaults, 
and my makefile doesn't have any coverage options.

The 632 qcc is not able to parse the 640 conf files. Make sure the 640 
qcc is being called.

If the underlying compiler has support for pre-compiled headers, the qcc 
conf files will be have the pch_support option set because the driver 
needs to know how far along in compilation stage to go, and what files 
to produces.

The second part is that it is not trying to build with code coverage. 
The new conf files have a gcc 'spec'-like syntax to allow the conf files 
to use rules so if the user specifies one option it will imply another. 
In this case the rule is if you specify -ftest-coverage, it will 
automatically link in the code coverage library (libgcov).

Regards,

Ryan Mansfield

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems