Review Request 114139: plugin/execute: add option to start app in specific shell

[Michal Humpula]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/114139/
-----------------------------------------------------------

Review request for KDevelop.


Repository: kdevplatform


Description
-------

Considering this document http://techbase.kde.org/Development/Tutorials/Building_An_Existing_Application, the official way to hack on the KDE apps is to setup separate environment and make install the application you are working on there. Currently you can specify an executable path in KDE launchers. That exe path can be path to shell script, that launches the app in/from correct env. But if you fill the shell script there instead of binary, you can't run a gdb against it.

So inspired by the similar option in gdb settings, this patch adds a shell option that NativeApp uses as launcher for the actual app.

There still might be the correct way to setup the launchers and honor the techbase document above, but I didn't find it. Suggestions welcomed.


Diffs
-----

  plugins/execute/executeplugin.h acf9d51 
  plugins/execute/executeplugin.cpp d3dd882 
  plugins/execute/iexecuteplugin.h 3ac3a37 
  plugins/execute/nativeappconfig.cpp 6f2dd8c 
  plugins/execute/nativeappconfig.ui 63954d3 
  plugins/execute/nativeappjob.cpp 4987e35 

Diff: http://git.reviewboard.kde.org/r/114139/diff/


Testing
-------


Thanks,

Michal Humpula

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20131126/a1ce836e/attachment.html>