Difference between revisions of "Projects/Digikam/Hacking with Eclipse"

Jump to: navigation, search
(some more explanation on how to get the projects into eclipse)
m (Text replace - "<code>" to "<syntaxhighlight lang="text">")
Line 2: Line 2:
  
 
Inside the folder that is used for the out-of-source build (must not be a child of the original source folder) do:
 
Inside the folder that is used for the out-of-source build (must not be a child of the original source folder) do:
<code>
+
<syntaxhighlight lang="text">
 
cmake -G "Eclipse CDT4 - Unix Makefiles" \
 
cmake -G "Eclipse CDT4 - Unix Makefiles" \
 
-DCMAKE_INSTALL_PREFIX=/usr/ \
 
-DCMAKE_INSTALL_PREFIX=/usr/ \

Revision as of 21:48, 29 June 2011

Creating the eclipse project with cmake as an out-of-source build:

Inside the folder that is used for the out-of-source build (must not be a child of the original source folder) do:

cmake -G "Eclipse CDT4 - Unix Makefiles" \
-DCMAKE_INSTALL_PREFIX=/usr/ \
-DKDE4_BUILD_TESTS=ON \
-DCMAKE_CXX_FLAGS=-pedantic \
-DCMAKE_C_FLAGS=-pedantic \
-DCMAKE_BUILD_TYPE=debug \
-DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE \
../../digikam/ <-- your source folder
</code>
This creates two eclipse projects. One in the build directory for building and one in the source folder for using Eclipse version control on the sources. Import these two projects in eclipse but ensure that you don't copy the files while importing (there is a checkbox in the import dialog).

KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal