Difference between revisions of "Digikam/Hacking with Eclipse"

Jump to: navigation, search
m (Text replace - "<code>" to "<syntaxhighlight lang="text">")
m (4 revisions imported)
 
(One intermediate revision by one other user not shown)
Line 11: Line 11:
 
-DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE \
 
-DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE \
 
../../digikam/ <-- your source folder
 
../../digikam/ <-- your source folder
</code>
+
</syntaxhighlight>
 
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).
 
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).

Latest revision as of 17:44, 18 March 2016

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

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).


This page was last edited on 18 March 2016, at 17:44. Content is available under Creative Commons License SA 4.0 unless otherwise noted.