Hi,

I am absolutely new to this mailing list, so pls. excuse me if I am telling 
bullshit ...

I am in the process of trying to understand why the hell I am not able to get 
the BareMetal plugin to debug an openOCD device (in a project using CMake). It 
seems as if I am always ending up in the standard GDB engine process and 
therefore never come to the point where my custom init commands (specified 
under BareMetal device) would be executed.
Giving a look at the qt-creator sources (at 
'https://gitorious.org/qt-creator/qt-creator.git') I have found the following 
piece of code (on the master branch):

// NBS TODO implement more than one runner
static IRunControlFactory *findRunControlFactory(RunConfiguration *config, 
RunMode mode)
{
    return ExtensionSystem::PluginManager::getObject<IRunControlFactory>(
        [&config, &mode](IRunControlFactory *factory) {
            return factory->canRun(config, mode);
        });
}

Not sure how crucial this piece of code is, but in case it plays a role in my 
case in running the debugging process it seems to me that it will always use 
the first IRunControlFactory in the global list of available factories, which 
in my case seems to be the standard DebuggerRunControlFactory rather than the 
desired BareMetalRunControlFactory.
Again, what I am observing might not be the right piece of code also because as 
far as I understand the BareMetal debugging works for Qbs projects, which 
actually confuses me a lot because the above piece of code (which btw can be 
found in file qt-creator/src/plugins/projectexplorer/projectexplorer.cpp, line 
#1870) seems not to be build system dependent.
Any enlightenment is welcome!

Thanks in advance,
Wolfgang


P.S.: I am running QtCreator 3.3.2 (opensource) (based on Qt 5.4.1 (GCC 4.6.1, 
64 bit)) on Linux with BareMetal plugin version 3.3.2.
_______________________________________________
Qt-creator mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/qt-creator

Reply via email to