Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

Title: RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

Yes, I tried it out and the environment is much more predictable with all the dependencies in as binary projects.  And given the number of CDT projects, the binary projects don't get in the way, that much J.

 

Thanks for looking into this for me.

 

- Doug

 

-----Original Message-----
From: Judy Green [mailto:jgreen@xxxxxxx]
Sent:
Monday, September 30, 2002 11:41 AM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

 

Hi Doug,

 

 

The PDE blurb follows:

1.      Simple (standalone) self-hosting uses external plug-ins for resolving plug-in references. It is simple, easy to manage and understand, and is completely adequate for standalone developers (those who do not use remote repositories to share their code with others).

2.      Binary project self-hosting introduces a step whereby external plug-ins are imported into the workspace as binary projects. They are still not meant to be modified and are usually hidden using a binary project filter in Package Explorer.

 

We at QNX, ran into this issue soon after we upgraded to Eclipse 2.0. At that time we felt that the better approach was the Binary project self-hosting.

 

We still believe that it suits our purposes best.

 

Let me know how it goes for you Doug.

 

-Judy

 

 

-----Original Message-----
From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx]
Sent: Friday, September 27, 2002 11:11 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

Thanks Judy,

 

Actually, I just ran through the PDE Guide which gives a great treatment of self-hosting.  So what we are recommending is binary project self-hosting, which, given the discussion in the Guide, suites our workflows the best.  I'll give it a try.

 

Cheers

- Doug

 

-----Original Message-----
From: Judy Green [mailto:jgreen@xxxxxxx]
Sent: Friday, September 27, 2002 4:21 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

 

Hi Doug,

 

Thanks for pointing this out. I'm looking into it and see if it fits the type of development structure that we decided upon.

 

We structured our development environment based on the following article.

 

 

Your solution does look to be a cleaner. From a first pass ... you do not *see* all the imported external plugins.

 

Can you still step onto the source for the platform code when linked in this manner? Any other differences or limitations that you have noticed?

 

 

I'll look into it more Monday.

 

Thanks again

 

-Judy

 

-----Original Message-----
From: Schaefer, Doug [mailto:dschaefer@xxxxxxxxxxxx]
Sent: Friday, September 27, 2002 3:48 PM
To: 'cdt-dev@xxxxxxxxxxx'
Subject: RE: [cdt-dev] Newbie instructions for getting up and running with the CDT

Hi Judy,

I was wondering why we weren't using the PDE to make setting up the CDT build easier.  Here's what I do to get things ready:

1) In the Preferences window->Plug-In Development->Target Platform, select all plug-ins.  This step really only has to be done once when you first run an Eclipse installation.

2) From dev.eclipse.org:/home/tools, Check Out As Project org.eclipse.cdt* although you probably want to leave out cdt.old since it is big and isn't used anymore.

3) In the Java perspective, select the above projects and do an Update Classpath.  Now, I'm not sure if this really needs to be done all of the time.  When I do this, most of the .classpath and .project files get updated.  If they were committed, you might not need to do this step at all.

And that's it.  Everything compiles.  From there, you can do the CDT build steps to create the distribution zips.  You can also run/debug the CDT in a "Run-Time Workbench".

I may be missing something but if the community allows me, I would like commit the changes to the .classpath and .project files to make this work.  Also, I'd like to fix the missing project dependency between debug.core and core.

Thanks,
- Doug

-----Original Message-----
From: Judy Green [mailto:jgreen@xxxxxxx]
Sent: Friday, September 27, 2002 9:18 AM
To: CDT Dev Mailing List (E-mail)
Subject: [cdt-dev] Newbie instructions for getting up and running with the CDT

Hi folks,

This is a quick list of steps to get you started with the CDT.
I'll be posting this to the website and to the Wiki Web within the week.

 

Note: Package names are valid as of today 27 Sept 2002. There will obviously
be more added in the future.

-Judy

¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨
Judy N. Green               Software Engineer
QNX Software Systems Ltd.   www.qnx.com
¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨¨°ºo§oº°¨¨¨

1)
Start Eclipse

2)
Open the Browse CVS Repository Perspective

3)
Check out the following CDT specific projects from the Eclipse CVS repo:
/home/tools
Anonymous
no password required

org.eclipse.cdt
org.eclipse.cdt.core
org.eclipse.cdt.core.linux
org.eclipse.cdt.core.qnx
org.eclipse.cdt.core.solaris
org.eclipse.cdt.core.win32
org.eclipse.cdt.debug.core
org.eclipse.cdt.debug.mi.core
org.eclipse.cdt.debug.mi.ui
org.eclipse.cdt.debug.ui
org.eclipse.cdt.launch
org.eclipse.cdt.ui
org.eclipse.cdt-feature

Optional:
the "org.eclipse.cdt.*.tests" packages can also be checked out.
In which case you will also need to import the org.junit package (and others
?) in the next step.
Additional instructions regarding testing will be coming soon.

 

4)
Import > External Plugins & Fragments > Plugins from the Runtime Workbench >

 

5)
Select the following from the list

org.apache.lucene
org.apache.xerces
org.eclipse.ant.core
org.eclipse.compare
org.eclipse.core.boot
org.eclipse.core.resources
org.eclipse.core.runtime
org.eclipse.debug.core
org.eclipse.debug.ui
org.eclipse.help
org.eclipse.platform
org.eclipse.search
org.eclipse.swt
org.eclipse.swt.win32 (or other platform specific project, will be added
through the next step)
org.eclipse.ui
org.eclipse.update.core

6)
Then press "Add Required Plugins" button.
This will add any other plugins that are required by the selected ones
  e.g. platform specific such as org.eclipse.swt.win32

 

To Build the CDT from within Eclipse

1)
 Browse to the org.eclipse.cdt package directory

2)
 Edit the "about.mappings" file to indicate the build number
    # e.g. "0=<year><month><date>"
    0=20020926

3)
Browse to the org.eclipse.cdt-feature package directory

4)
Open the "feature.xml" file

5)
Select the "Package" button from the Overview Page

6)
From the dialog that is presented select the following IN ORDER. Notice the
numbers that appear beside the selected items.

1) clean
2) init
3) build.jars
4) build.update.jar
5) build.zips
6) zip.distribution
7) build.sources
8) zip.sources

Note items 7 & 8 are optional and only if you want to package the sources.
They also take a fairly large component of time.

When the build is complete there will be a binary
distribution zip file and (optionally) a sources zip file
e.g.
org.eclipse.cdt_20020926_1.0.0.bin.dist.zip  ... zipped features and plugins
org.eclipse.cdt_20020926_1.0.0.src.zip        ... zipped sources
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top