Re: [cdt-debug-dev] Remote debugging development in CDT

["Alain Magloire" <alain@xxxxxxx>]

> 

spamming cdt-core-dev

> 
> >
> >In the end,  the user experience of the CDT will depend on
> >the code, patches and time donated by the developers.
> 
> Hi!
> 
> I agree 100%. I just wish that we (Tensilica) were pushing in an area where 
> our work was of more interest. Beyond support for our own hardware 
> languages and views we are doing build model, and extension of the platform 
> to support our debugger, two compilers and simulators. We don't have time 
> to wait for TimeSys's build model solution and ours did not generate much 
> interest.
> 

I do not agree with this, your proposal had some good points.
Some folks was looking at TimeSys because it seems to address some
prerequisites:
- Be able to instrument code, for example to go from
  .cc --> .i --> .o
  Need to put hooks in the code, after the preprocessing stage
- Different stage of building
- Different configurations/settings, per build


For example, QNX C/C++ projects will not use the default CDT builder.
QNX C projects have there own builder that will take over the build process.

Same thing for the "GNUDE" 8-), for example you are debugging gcc or gdb
and you want to use the CDT IDE, you probably do not want to use the default
CDT builder, but rather the "GNUDE" which is more an adapter to the build
model, spawing all the GNU autotools(automake, autoconf, etc ..).

Trying to impose yet another build mechanism to say, gdb/gcc developers
and they will drop the IDE in a heartbeat. But if we propose an API
that can be adapt to different scenarios __and__ a solid default implementation
of this API(CDT default build), probably the best of both worlds.


> That leaves me (the non-lurker) answering the questions from folks like the 
> original poster on this thread and posted what we learn of doing the 
> extension. Stay tuned, explanation of how to get your own target remote 
> version working with the debug model coming soon.

Thanks, it was good reading.  Hopefully we can address some of the issues
in the other releases.  Improvement by iterations 8-)