# HG changeset patch # User timkelly # Date 1238168177 18000 # Node ID 6b79ffb176c54eb8f5163bddaf001ddf45c1f203 # Parent f330c1e8a4f31b436cbcfea734415740d6ae08f7 Update to describe how SFO CDK works diff -r f330c1e8a4f3 -r 6b79ffb176c5 carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/background.htm --- a/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/background.htm Wed Mar 25 11:55:19 2009 -0500 +++ b/carbidesdk/com.nokia.carbide.cpp.sdk.doc.user/html/gettingStarted/background.htm Fri Mar 27 10:36:17 2009 -0500 @@ -12,7 +12,7 @@
Carbide.c++ is built on the Eclipse platform. The Eclipse components used are:
This section will describe how to set up a basic Eclipse development environment to develop a plugin against the Carbide.c++ development environment.
-Carbide.c++ is developed against the Eclipse 3.4 release build. You can download the build -here. Carbide.c++ is only tested and supported on the Windows platform.
-You can extract the Eclipse platform anywhere you like.
-NOTE When you launch eclipse, choose a workspace location without spaces. This will help to prevent build issues later on with Symbian SDKs.
-Carbide.c++ is developed against the Eclipse 3.4 release build which includes the Java Development Tools (JDT) and Plug-in Development Environment (PDE). You will need these items as well as the Carbide.c++/CDT source code to develop Eclipse/Carbide.c++ plug-ins. If you want to install the CDK you will need to run the Software Updates under the Help menu to update your installation to include the CDK.
+For more information on running the Software Updater please see the page Updating Carbide.c++.
+Once you have your Eclipse environment extracted and launched, you can set up your Target Platform to have your fresh installation reference all the Carbide.c++/CDT/Eclipse plugins.
-The Eclipse Target Platform feature allows you to compile and run against a different Eclipse installation than the -one you're using for development. In this case you'll be targeting the Carbide.c++ installation. The Target Platform is a workspace-wide setting, so you may want to dedicate a separate workspace for your Carbide.c++ plugin development.
- +Once you have your Carbide environment updated to include the CDK, you can create new Eclipse plug-in projects and debug the Carbide.c++ sources. How to create eclipse plug-ins is beyond the scope of this demonstration. If you want to debug any of the Carbide.c++ or Ecilpse platform source follow these steps to verify your CDK isntallation:
You are now ready to import or create new projects into your Eclipse workspace.
- -There are two example plugins you can import and examine as examples of Carbide.c++ API usage.
+You can import any of the plug-ins in Carbide.c++ and examine the source code. However, the SDK provides a plug-in you can import and examine as an example of Carbide.c++ API usage.
You can import these plugins into your workspace and view/debug all the source to get a better understanding of the -Carbide.c++ APIs in a functional plugin.
+You can import this and other plugins into your workspace and view/debug all the source to get a better understanding of the +Carbide.c++ APIs in a functional plugin. Plesae see the page on setting up your development environment for information on how to import a source project.
Note that the example plugins were built with JRE1.5, you will likely receive errors with JRE1.6. Select Window > Preferences > Java > Installed JREs to add currently installed JREs and select the JRE to use.
-com.nokia.carbide.cpp.leavescan
and
- com.nokia.carbide.cpp.sdk.examples
plugins.When you are done importing you should have new plugins in your workspace and be able to view the
+ sources for both plugin projects. Your workspace should look something like this:
+
+
The menu items contributed by the Examples plugin are not visible by default in the Carbide.c++ program. To show the missing menu, follow these steps:
Click OK, and you should now see the Carbide menu in the menu bar.
+Click OK, and you should now see the Carbide menu in the menu bar. You can now examine the source code and run it in the debugger. See debugging a debugging a Carbide.c++ plug-in for information on setting up a plug-in debug session.