[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-debug-dev] Hacks to CDT to support Zylin Embedded CDT plugin
|
>
> >Excellent!!
> >Then did we cover all your requirements ?
>
> Besides various bugfixes, pretty much, yes.=20
>
> >Minus the CygwinTranslator path(move to 3.0 target milestone)
>
> Bump! :-)
>
> Hmmm....
>
> Do versions matter?
>
> For embedded development, it doesn't seem like it is going to be
> possible to seperate CDT and the plugin in the forseeable future.
>
> Eclipse supports side-by-side install of the *entire* Eclipse and=20
> sharing of workspaces across Eclipse installations, so this is not the
> end of the world.
>
> What pragamtic solution could we come up with to reduce my CDT changes
> to pure bugfixes?
>
Integration points.
In the CDT we have created a variety of extension points to make
integration possible:
- error parsers
- binary parsers
- debug
etc ..
It allow to plugin different behaviour when the default behaviour
will not do for certain enviroment.
Where/how to do this?? dunno, something to look for the future.
> Basically we need to:
>
> - identify all the places where paths enter/exit the Eclipse universe
> and Eclipse host OS !=3D tool host OS. E.g develop with Eclipse
> Windows/CygWin, or Eclipse Windows + Linux hosted GDB/GCC.
> - Provide some sort of translation hook that can either be supported in
> a plugin, or minimally a way to only require a ugly hack in a single
> spot or two.
>
> For those that wish to view my changes to CDT:
>
> http://zylin.com/pipermail/zylin-discuss_zylin.com/2004-November/000057.html
>
On bird eyes view, the patch seems to be to widespread touching/changing things all over.
Then why not make the "PathTranslator" and extension
point, a service that can be taken from the core allowing, different
plugins like debug, make etc .. to take advantage of.
