Re: [C++] Configuring an Eclipse C++ IDE for Tuscany Development

2006-07-25 Thread Pete Robbins

Great stuff. I will go back to using CDT now the automake is kind of stable
;-)

At one point I checked in cdt project files into svn. Do you think this is
worthwhile?

Cheers,


On 21/07/06, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:


I just finished configuring a Tuscany C++ development environment on my
Linux machine with the Eclipse C++ Tools.

It's very easy to set up and the C++ tools work pretty well. I thought
it would be useful to share the steps I went through on Redhat Linux.

1. Download and install Eclipse 3.2 and the C/C++ Development tools

- Point your Web browser to http://www.eclipse.org/callisto/c-dev.php
for the Eclipse C++ / CDT home page.
- Download the Eclipse 3.2 Platform Runtime (33 Mb) from

http://download3.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/callisto.php
- Run tar xzf eclipse-platform-3.2-linux-gtk.tar.gz to extract the
eclipse runtime
- Make sure you have a Java JRE 1.4.2 or higher, it is required to run
eclipse.
- Run eclipse/eclipse to start eclipse
- From the top menu bar click help / software updates / find an install
- In the install dialog select search for new features to install,
click next
- In sites to include... select Callisto Discovery Site, click next
- In select the features to install, select Callisto Discovery Site /
C and C++ development, click next
- Read and accept the Eclipse license agreement, press finish, this will
download and install the CDT plugins
- Restart your Eclipse workbench

2. Create Eclipse C/C++ projects for the SDO and SCA runtimes

SDO
- From the top menu bar, select Window / Open Perspective / Other /
C/C++ to open the C/C++ development perspective
- Select File / New / Standard Make C++ Project
- In the New Project dialog, choose a Project name: sdo
- Uncheck Use default location, click Browse and select the
tuscany/cpp/sdo folder (where you have checked out the Tuscany C++ SDO
code), click Next
- In the Make Builder tab, change the following:
- Check Stop on first build error
- Check Build on resource save, and change the Make build target to
blank (instead of the default all)
- Change the Incremental Build target to install (instead of all)
- In the C++ Index tab, select Fast C/C++ Indexer
- Press finish, wait for the workspace to build.

Note:
With this setup Eclipse will not generate the makefiles, it will only
run make to build/rebuild the projects. The makefiles still need to be
generated from the command line using automake, configure etc. It's
probably better to do this from the command line anyway, but you don't
need to do it very often, when you change folder structures for example.

SCA
Repeat the same steps to create an sca project.

After you complete these steps, you should have a nice working C++
development environment, loaded with the Tuscany C++ code.

The C++ editor supports code assist, syntax highlighting, some
refactoring, when you make changes to your code, builds get triggered
automatically in the background and any errors are nicely reported in
the C++ editor. The debugger fronts gdb, works well and allows me to
step through the Tuscany runtime, inspect variables etc.

Hope this helps. Happy coding...

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Pete


[C++] Configuring an Eclipse C++ IDE for Tuscany Development

2006-07-21 Thread Jean-Sebastien Delfino
I just finished configuring a Tuscany C++ development environment on my 
Linux machine with the Eclipse C++ Tools.


It's very easy to set up and the C++ tools work pretty well. I thought 
it would be useful to share the steps I went through on Redhat Linux.


1. Download and install Eclipse 3.2 and the C/C++ Development tools

- Point your Web browser to http://www.eclipse.org/callisto/c-dev.php 
for the Eclipse C++ / CDT home page.
- Download the Eclipse 3.2 Platform Runtime (33 Mb) from 
http://download3.eclipse.org/eclipse/downloads/drops/R-3.2-200606291905/callisto.php
- Run tar xzf eclipse-platform-3.2-linux-gtk.tar.gz to extract the 
eclipse runtime
- Make sure you have a Java JRE 1.4.2 or higher, it is required to run 
eclipse.

- Run eclipse/eclipse to start eclipse
- From the top menu bar click help / software updates / find an install
- In the install dialog select search for new features to install, 
click next

- In sites to include... select Callisto Discovery Site, click next
- In select the features to install, select Callisto Discovery Site / 
C and C++ development, click next
- Read and accept the Eclipse license agreement, press finish, this will 
download and install the CDT plugins

- Restart your Eclipse workbench

2. Create Eclipse C/C++ projects for the SDO and SCA runtimes

SDO
- From the top menu bar, select Window / Open Perspective / Other / 
C/C++ to open the C/C++ development perspective

- Select File / New / Standard Make C++ Project
- In the New Project dialog, choose a Project name: sdo
- Uncheck Use default location, click Browse and select the 
tuscany/cpp/sdo folder (where you have checked out the Tuscany C++ SDO 
code), click Next

- In the Make Builder tab, change the following:
 - Check Stop on first build error
 - Check Build on resource save, and change the Make build target to 
blank (instead of the default all)

 - Change the Incremental Build target to install (instead of all)
- In the C++ Index tab, select Fast C/C++ Indexer
- Press finish, wait for the workspace to build.

Note:
With this setup Eclipse will not generate the makefiles, it will only 
run make to build/rebuild the projects. The makefiles still need to be 
generated from the command line using automake, configure etc. It's 
probably better to do this from the command line anyway, but you don't 
need to do it very often, when you change folder structures for example.


SCA
Repeat the same steps to create an sca project.

After you complete these steps, you should have a nice working C++ 
development environment, loaded with the Tuscany C++ code.


The C++ editor supports code assist, syntax highlighting, some 
refactoring, when you make changes to your code, builds get triggered 
automatically in the background and any errors are nicely reported in 
the C++ editor. The debugger fronts gdb, works well and allows me to 
step through the Tuscany runtime, inspect variables etc.


Hope this helps. Happy coding...

--
Jean-Sebastien


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]