Project Home
Project Home		 Trackers
Trackers		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
IDE/Discussion/General/Recommended Reading?/List of Posts
Forum Topic - Recommended Reading?: (5 Items)
   
Update
Norton Allen
06/27/2008 11:27 AM
post9789
Recommended Reading?   
I've used Eclipse in various incarnations for a few years and find myself continuously frustrated by the cursory 
documentation, and I'm wondering if anyone can recommend particularly good references. The kinds of questions that nag 
at me are:

-What is the difference between the different project types?
-Are any project types compatible with command-line building?
-How portable are Eclipse projects of various types?
  -which metadata files should be stored in SCM (specific to the project no matter where it's built) and which are more 
local preferences?
  -if I have an existing project without metadata, what's the best way to import it into Eclipse?
  -are projects portable between different versions of Eclipse?
-How should I organize a complex development?
  -At what granularity should a large job be broken into projects?
  -How do different projects in the same workspace interact?
  -Can I create more than one executable in the same project?
Elena Laskavaia
06/27/2008 11:39 AM
post9791
Re: Recommended Reading?   
These are very good questions and I am going to submit it as feature 
request for our documentation with all these questions.
Here are some sort answers (I will be talking about QNX IDE not eclipse 
in general)

Norton Allen wrote:
> I've used Eclipse in various incarnations for a few years and find myself continuously frustrated by the cursory 
documentation, and I'm wondering if anyone can recommend particularly good references. The kinds of questions that nag 
at me are:
>
> -What is the difference between the different project types?
>   
We have 3 project types: Standard make, Managed project and Qnx Managed 
Project.
Standard make - is project that can run command line make, all build 
features are managed by user in makefiles, except commands to run make 
itself from IDE,
Managed project - is original CDT project which are managed from IDE 
100%, in IDE 4.0.1 they cannot be build from command line, in IDE 4.5 
makefile can be generated from they to build from command line
Qnx Managed Project - is based on QNX recursive makefiles, it is managed 
from IDE or from Makefiles, but makefiles are require very low 
maintenance because most settings are automatic. Can be build from 
command line.
> -Are any project types compatible with command-line building?
>   
see above
> -How portable are Eclipse projects of various types?
>   -which metadata files should be stored in SCM (specific to the project no matter where it's built) and which are 
more local preferences?
>   
.project, .cproject and .cdtproject (in old versions) should be stored 
with the project, metadata aka workspace/.metadata should never be
>   -if I have an existing project without metadata, what's the best way to import it into Eclipse?
>   
using Import wizard. Alternately you can just create a link folder, in 
this case it is not going to copy source code.
>   -are projects portable between different versions of Eclipse?
>   
they should be, there some bugs but in general you should expect to have 
automatic import
> -How should I organize a complex development?
>   -At what granularity should a large job be broken into projects?
>   
Usually one binary/shared library per project (plus all multi 
platform/debug variants)
>   -How do different projects in the same workspace interact?
>   
You can add dependency which can affect build/make dependencies. Usually 
you add explict dependency on particular parts, for example shared libraries
>   -Can I create more than one executable in the same project?
>   
If you have standard make project yes.
>
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post9789
>
>
Norton Allen
06/30/2008 9:49 AM
post9856
Re: Recommended Reading?   
Thanks, Elena. That does help with the basic landscape. Of course it raises more questions for me!

With regard to project types, I'd love to see some discussion comparing the  project types and indicating the relative 
advantages and disadvantages, what you can and can't do with a particular project type. Coming from years of command 
line make development, the limits on project complexity are pretty much whatever you want to code into the Makefile(s). 
Eclipse projects impose real restrictions and require some adjustments. That may be a good thing, but it would be 
helpful to understand the issues before diving in rather than discovering them by trial and error.

I have also seen command options to "Convert to C/C++ make project". What does that do? Does it behave differently for a
 QNX project versus a CDT project? Is there a simple way to do other project type conversions? e.g. if I have a standard
 make project, what would be the simplest way to convert it to a QNX C++ project?
Elena Laskavaia
07/02/2008 9:59 AM
post9917
Re: Recommended Reading?   
"Convert to C/C++ make project" you would use to convert project that 
does not have any C specific nature, to a Makefile project.
It would not do any real conversion, if it is already CDT or QNX project 
(I think, but you can try).
Conversion from makefile project to anything else if pretty much 
impossible because makefile can be be "whatever" as you mentioned.

Simplest way to convert would be to create a QNX new project, move all 
the sources in the and try to build it. This again assumes that all 
sources are for one executable/library. You can then modify options of 
compiler, linker and so on using QNX project properties. To keep this 
structure you have to commit sources and infrastructure directories and 
makefiles into source control system. CVS and Subversion are recommended 
because they have the best integration with IDE.

The best way to share source code between project is to separate them in 
libraries, then you can link them with different binaries. This way you 
have lots of projects but IDE provides a way to manage it by using 
Working sets and hiding some projects.

If you need information about qnx recursive makefiles you can find it 
here (this is more non-IDE use of them):
http://www.qnx.co.jp/developers/docs/6.3.2/neutrino/prog/make_convent.html#SPEC
Elena Laskavaia
04/03/2009 3:31 PM
post26013
Re: Recommended Reading?   
I finally wrote an article about Project and Build in QNX IDE.
Please check link below:
http://community.qnx.com/sf/wiki/do/viewPage/projects.ide/wiki/ProjectsBuildAndIDE

Return


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