Difference between revisions of "Debugging using Kdevelop"

From Yade

Line 8: Line 8:
 
If for some reasons this file does not work for you, you can easily generate a new Yade project after deleting the current yade.kdev4. Start empty kdevelop sesion and "import" a project, then select the yade directory, but don't give any "project" file *.kdev4 (the old yade.kdevelop project for kdev3 cannot be read either), as it will have to be generated automaticaly. Select project type "custom build", then go to project option and set build executable "scons". At this point, you can compile from kdevelop, get nice error output with links to where the errors are, etc. There is also a rich class and member description, auto-completion, display of functions signatures,... as shown in screenshots below.
 
If for some reasons this file does not work for you, you can easily generate a new Yade project after deleting the current yade.kdev4. Start empty kdevelop sesion and "import" a project, then select the yade directory, but don't give any "project" file *.kdev4 (the old yade.kdevelop project for kdev3 cannot be read either), as it will have to be generated automaticaly. Select project type "custom build", then go to project option and set build executable "scons". At this point, you can compile from kdevelop, get nice error output with links to where the errors are, etc. There is also a rich class and member description, auto-completion, display of functions signatures,... as shown in screenshots below.
   
Also check page on [https://yade-dem.org/wiki/Debugging_using_KdevelopDebugging_using_Kdevelop debugging].
+
Also check page on [https://yade-dem.org/wiki/Debugging_using_Kdevelop].
   
 
[[Image:kdev4_2.png|800px|Compiling from kdevelop will display links to where the errors are, as well as different formated listings of warningsn FIXMEs, TODOs,...]]
 
[[Image:kdev4_2.png|800px|Compiling from kdevelop will display links to where the errors are, as well as different formated listings of warningsn FIXMEs, TODOs,...]]
 
   
 
==Procedure for Kdevelop 3==
 
==Procedure for Kdevelop 3==

Revision as of 19:59, 1 July 2010


Update for Kdevelop 4

Yade sources come with a yade.kdev4 file that you can open with kdevelop 4.

Passing the pointer on members will display informations and links to navigate in the sources.

If for some reasons this file does not work for you, you can easily generate a new Yade project after deleting the current yade.kdev4. Start empty kdevelop sesion and "import" a project, then select the yade directory, but don't give any "project" file *.kdev4 (the old yade.kdevelop project for kdev3 cannot be read either), as it will have to be generated automaticaly. Select project type "custom build", then go to project option and set build executable "scons". At this point, you can compile from kdevelop, get nice error output with links to where the errors are, etc. There is also a rich class and member description, auto-completion, display of functions signatures,... as shown in screenshots below.

Also check page on [1].

Compiling from kdevelop will display links to where the errors are, as well as different formated listings of warningsn FIXMEs, TODOs,...

Procedure for Kdevelop 3

When compiling yade for the first time, please do it from command line, so that a file scons.config will contain your compilation settings. After that you can start working using kdevelop. You can run kdevelop with command:

cd yade-0.11.0
kdevelop Yade.kdevelop

Or running it directly from konqueror by clicking on file Yade.kdevelop. When kdvelop starts for the first time it will ask to populate the project. Let it do this:

Kdevelop populate.png

Then you will need to go into project options to configure your paths and set number of processors to be used during compilation (because, unfortunately kdevelop overrides scons jobs setting):

Kdevelop options.png

Kdevelop jobs.png

Kdevelop runpaths.png

Then, after compiling yade you can try running it, and debugging, which should work without problems.

Kdevelop debugging.png