Some help with launch configurations

[Andreas Pakulat]

On 10.07.09 15:43:36, Kishore wrote:
> On Friday 10 Jul 2009 1:38:03 pm Vladimir Prus wrote:
> > On Friday 10 July 2009 Kishore wrote:
> > I am not exactly sure about dialog -- that
> > combo appears to only select what settings you want to edit -- it does not
> > change how the launch configuration is launched -- you pick the relevant
> > item from the menu. However, it's a bit confusing to myself, too.
> > Andreas, can you clarify what this combobox is supposed to mean?
> 
> If the combobox in the dialog is meant to "create" the tab below it. would it 
> not be better to have them as tabs that always exist and just discard the 
> "Launch Mode" combobox?
 
Well, IMHO its not so nice to have 8 tabs there just because there are 8
possible launch modes. And eventually even more if there are more launchers
for a given launchmode (think of integrating gdb+msvc-debug on win32 for
Debugging native apps). Thats why the tabs are added/removed based on the
launchmode.
 
> Also, from your comments its seems to be that the number of items that are 
> displayed in this combo box are also the items that appear in the menu. And 
> the various possibilities are based on the plugins that are currently loaded. 
> right?

Right, a plugin can register custom launch modes, custom launchers and
custom launch types with the framework. Additional launch modes will create
new menu entries in the Run menu.

> > > In my particular case, I do a lot of embedded systems and am interested
> > > in maintaining two build folders. One for building the application in for
> > > the x86 platform and another for the arm platform.
> > >
> > > When I run or debug my application that is built for arm, I need to
> > > launch openocd which is a gdb server that connects to the arm device over
> > > a JTAG interface. arm-gdb then connects to openocd. Later i want openocd
> > > to exit as i stop debugging.
> > >
> > > Can i in some way achieve this with the launch configurations workflow?
> >
> > It will require creating gdb/shell scripts and specifying that in debugger
> > configuration. Say, gdb script might have:
> >
> > 	shell whatevercommand &
> >     target remote <xxx>
> >
> > However, I don't think anobody tested this with KDevelop4, so you are on
> > thin ice. Eventually, we'll have 'remove application' launch type that will
> > make this easy.
> 
> The one thing that i immediately noticed with the cmake support is that it 
> needs to provide the additional cmake configuration that is provided by cmake-
> gui when creating the build folder. Perhaps, through an "Advanced" button.

Not sure what you mean with that. Opening a cmake project asks you already
for the builddir for that project. If you have multiple builddirs you can
configure them via Project->Project Configuration...->CMake and switch the
active one there. 

I'm planning to have a more generic way of switching between build
configurations for a project so that the switching can be put into a
non-cmake-specific place in the GUI. But thats something for 4.1 probably.

Andreas

-- 
You will obey or molten silver will be poured into your ears.