Slicer3::Eclipse - Revision history

Senseneyj: /* Creating an Eclipse Project for Slicer3: */ typo in dir name

2012-12-21T13:37:49Z

Creating an Eclipse Project for Slicer3:: typo in dir name

Clisle: /* Note to Snow Leopard users */

2010-10-15T14:32:02Z

Note to Snow Leopard users

Clisle: /* Understanding Slicer's startup process */

2010-10-15T14:27:50Z

Understanding Slicer's startup process

Belhachemi: /* Howto Setup Eclipse – Slicer3 Development Environment: */

2010-10-08T19:47:14Z

Howto Setup Eclipse – Slicer3 Development Environment:

Belhachemi: /* Howto Setup Eclipse – Slicer3 Development Environment: */

2010-10-08T19:22:12Z

Howto Setup Eclipse – Slicer3 Development Environment:

Belhachemi: /* Howto Setup Eclipse – Slicer3 Development Environment: */

2010-09-23T19:13:19Z

Howto Setup Eclipse – Slicer3 Development Environment:

Belhachemi: /* Howto Setup Eclipse – Slicer3 Development Environment: */

2010-09-16T13:38:58Z

Howto Setup Eclipse – Slicer3 Development Environment:

Belhachemi: /* Understanding Slicer's startup process */

2010-09-15T17:55:21Z

Understanding Slicer's startup process

Belhachemi: /* Debugging with Eclipse Instructions */

2010-09-15T17:53:57Z

Debugging with Eclipse Instructions

Belhachemi: /* Continuing with Debugging under Eclipse */

2010-09-15T17:53:01Z

Continuing with Debugging under Eclipse

@@ Line 102: / Line 102: @@
 '''Step 6:''' Enter the make command we want to use.  Notice that we specified four jobs (to build faster) and specified the location to use as the current directory for the build:
-:'''make -j 4 -C Users/dot/Projects/slicers/trunk-012210/Slicer3-build'''
+:'''make -j 4 -C /Users/dot/Projects/slicers/trunk-012210/Slicer3-build'''
 '''Step 7:''' In the same pop-up window, enter the build directory again in the "Build location" dialog (same pathname as you just entered above in step 6).  Now you can click OK to accept these entries.  Eclipse should start building the project right away.  You can see the C++ compilations go by in the "Console" tab at the bottom.   We are using Eclipse to fire off the makefile built by cmake.  This means we can still go outside Eclipse and type "make" by hand anytime.  Eclipse just knows how to fire off the make when necessary.

@@ Line 145: / Line 145: @@
 == Note to Snow Leopard users ==
 In the Summer of 2010, we found moving to Snow Leopard caused debugging to stop working.  The newest (nightly build) of Eclipse was needed to get breakpoints to actually force the program to stop again.  Debugging worked without tweaking Eclipse for systems running Tiger and Leopard.  However, the 64-bit only mode of Snow Leopard meant a 64-bit Eclipse is needed for debugging.   It is expected that these issues will be resolved in the release version of Eclipse 3.6 (Helios). Do remember that debugging only works using a 64-bit version of Eclipse  on Snow Leopard (because the build is now a 64-bit build.)
 =Old description from 2008=

@@ Line 137: / Line 137: @@
 #% source ./Slicer3-build/bin/Slicer3SetupPaths.sh
-#% ./eclipse/eclipse &
+#% ~/Desktop/eclipse/eclipse &
 '''Step 2:''' Then in the Eclipse window, open the Project/Properties by right-clicking on the Project Explorer entry for your Slicer build.  Then select the "Run/Debug Settings" entry.  We want to set the executable to point to "Slicer3-real" instead of "Slicer3".  This plus running the script in the shell Eclipse was started from *may* be enough to get the debugger started on Slicer.

@@ Line 37: / Line 37: @@
   Slicer4                             (3D Slicer source)
   Slicer4-SuperBuild                  (Dependencies source+binary)
-  Slicer4-SuperBuild/Slicer3-build    (3D Slicer binary)
+  Slicer4-SuperBuild/Slicer-build     (3D Slicer binary)
 Go to the 3D Slicer binary directory and generate your eclipse project files
-  cd Slicer4-SuperBuild/Slicer3-build
+  cd Slicer4-SuperBuild/Slicer-build
   cmake -G"Eclipse CDT4 - Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ../../Slicer4

@@ Line 30: / Line 30: @@
   mkdir Slicer4-SuperBuild
   cd Slicer4-SuperBuild
-  cmake -DSlicer3_USE_KWWIDGETS:BOOL=OFF -DSlicer3_USE_PYTHON:BOOL=OFF -DSlicer3_USE_QT:BOOL=ON -DSlicer3_USE_PYTHONQT:BOOL=OFF ../Slicer4/SuperBuild
+  cmake -DSlicer_USE_KWWIDGETS:BOOL=OFF -DSlicer_USE_PYTHON:BOOL=OFF -DSlicer_USE_QT:BOOL=ON -DSlicer_USE_PYTHONQT:BOOL=OFF ../Slicer4/SuperBuild
   make
   cd ..

@@ Line 26: / Line 26: @@
 CASE: using Superbuild (Slicer 4.0)
-  svn co http://svn.slicer.org/Slicer3/trunk Slicer3
+  svn co http://svn.slicer.org/Slicer4/trunk Slicer4
-  cd Slicer3-SuperBuild
+ mkdir Slicer4-SuperBuild
-  cmake -DSlicer3_USE_KWWIDGETS:BOOL=OFF -DSlicer3_USE_PYTHON:BOOL=OFF -DSlicer3_USE_QT:BOOL=ON -DSlicer3_USE_PYTHONQT:BOOL=OFF ../Slicer3/SuperBuild
+  cd Slicer4-SuperBuild
   make
   cd ..
 You will find 2+1 folders in your directory
-  Slicer3                             (3D Slicer source)
+  Slicer4                             (3D Slicer source)
-  Slicer3-SuperBuild                  (Dependencies source+binary)
+  Slicer4-SuperBuild                  (Dependencies source+binary)
-  Slicer3-SuperBuild/Slicer3-build    (3D Slicer binary)
+  Slicer4-SuperBuild/Slicer3-build    (3D Slicer binary)
 Go to the 3D Slicer binary directory and generate your eclipse project files
-  cd Slicer3-SuperBuild/Slicer3-build
+  cd Slicer4-SuperBuild/Slicer3-build
-  cmake -G"Eclipse CDT4 - Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ../../Slicer3
+  cmake -G"Eclipse CDT4 - Unix Makefiles" -D CMAKE_BUILD_TYPE=Debug ../../Slicer4

← Older revision		Revision as of 13:38, 16 September 2010
Line 59:		Line 59:


−	Add a -j<cores> to your make command (Properties->C/C++MakeProject)	+	* Add a -j<cores> to your make command (Properties->C/C++MakeProject)
		+	* Under "Window->Preferences->General->Editors->Text Editors" please check "Insert spaces for tabs"

	=Revised Howto Setup Eclipse to build/edit the Slicer3 Development Environment (Eclipse 3.5)=		=Revised Howto Setup Eclipse to build/edit the Slicer3 Development Environment (Eclipse 3.5)=

@@ Line 128: / Line 128: @@
 ==Understanding Slicer's startup process==
-The executable xxxx/Slicer3-build/Slicer3 is not the real program, instead it is just a "launcher".   This executable sets up a bunch of paths and environment variables, then launches the real executable.   The "real" Slicer3 program is stored in:  xxxx/Slicer3-build/bin/Slicer3-real.    So when we are asking Eclipse to run Slicer under the debugger, we really want Eclipse to startup and attach to an instance of "Slicer3-real".
+The executable ./Slicer3-build/Slicer3 is not the real program, instead it is just a "launcher".   This executable sets up a bunch of paths and environment variables, then launches the real executable.   The "real" Slicer3 program is stored in: ./Slicer3-build/bin/Slicer3-real. So when we are asking Eclipse to run Slicer under the debugger, we really want Eclipse to startup and attach to an instance of "Slicer3-real".
-'''Step 1:''' There is a script in xxx/Slicer3-build/bin/Slicer3SetupPaths.sh or Slicer3SetupPaths.csh which sets up the same paths as the launcher.  If we run this script in a shell window (on Mac or Linux), then run eclipse from the same shell, we will have the environment defined.  This is how to try it the first few times, but there is a cleaner way we will try after we know debugging is working.   So if you are on either a Mac or Linux, open a shell and source this setup script, please.
+'''Step 1:''' There is a script in ./Slicer3-build/bin/Slicer3SetupPaths.sh or ./Slicer3-build/bin/Slicer3SetupPaths.csh which sets up the same paths as the launcher.  If we run this script in a shell window (on Mac or Linux), then run eclipse from the same shell, we will have the environment defined.  This is how to try it the first few times, but there is a cleaner way we will try after we know debugging is working.   So if you are on either a Mac or Linux, open a shell and source this setup script, please.
 Then in the same shell, start eclipse.  It will be something like this:
-#% source /usr/local/slicers/trunk/Slicer3-build/bin/Slicer3SetupPaths.sh
+#% source ./Slicer3-build/bin/Slicer3SetupPaths.sh
-#% ~/Desktop/eclipse/eclipse &
+#% ./eclipse/eclipse &
 '''Step 2:''' Then in the Eclipse window, open the Project/Properties by right-clicking on the Project Explorer entry for your Slicer build.  Then select the "Run/Debug Settings" entry.  We want to set the executable to point to "Slicer3-real" instead of "Slicer3".  This plus running the script in the shell Eclipse was started from *may* be enough to get the debugger started on Slicer.

@@ Line 124: / Line 124: @@
 # build Slicer totally first the normal way, either with cmake or getbuildtest.tcl.
 # Create the project in Eclipse by referring to the makefile and entering an external make command line
 Assuming that Slicer is building under Eclipse, we'll take off from this point on:
@@ Line 145: / Line 143: @@
 == Note to Snow Leopard users ==
 In the Summer of 2010, we found moving to Snow Leopard caused debugging to stop working.  The newest (nightly build) of Eclipse was needed to get breakpoints to actually force the program to stop again.  Debugging worked without tweaking Eclipse for systems running Tiger and Leopard.  However, the 64-bit only mode of Snow Leopard meant a 64-bit Eclipse is needed for debugging.   It is expected that these issues will be resolved in the release version of Eclipse 3.6 (Helios). Do remember that debugging only works using a 64-bit version of Eclipse  on Snow Leopard (because the build is now a 64-bit build.)
 =Old description from 2008=

@@ Line 117: / Line 117: @@
 == Continuing with Debugging under Eclipse==
-At this point, you should be able to build Slicer using Eclipse and run Slicer from inside Eclipse. If you want to debug Slicer interactively under Eclipse, there is a bit more configuration to perform.  Please continue with the debugging instructions found at [http://wiki.slicer.org/slicerWiki/index.php/Slicer3::Debugging_with_Eclipse_Instructions http://wiki.slicer.org/slicerWiki/index.php/Slicer3::Debugging_with_Eclipse_Instructions].
+At this point, you should be able to build Slicer using Eclipse and run Slicer from inside Eclipse. If you want to debug Slicer interactively under Eclipse, there is a bit more configuration to perform. Please continue with the debugging instructions found below.
 =Debugging with Eclipse Instructions=