Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] DSF/GDB: How to provide a custom content for a platform view?

On 20 May 2010 20:25, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
> Mikhail,
> *Every* package should be exported. Period. That is the policy for all
> projects. If there are any unexported packages, it's just an
> oversight. I can double check all the dsf plugins, or if you want to do it
> and update the projects, that would be great.

Gosh, I wasn't aware of that, however a quick google confirmed what
you've said... From the horse's mouth, as it were:


> John
> At 01:47 PM 5/20/2010, Mikhail Khodjaiants wrote:
>> Thanks Pawel. So to make a simple addition to a view I need to write my
>> own debugger.
>> I hope Marc can answer my second question: what's the logic behind
>> exporting and not exporting some of the internal packages?
>> Regards,
>> Mikhail
>> On 20/05/2010 2:14 PM, Pawel Piech wrote:
>>> The intention is that the adapter factory would be custom written for
>>> each debugger, because it's a place to add hooks to customized adapters.
>>>  But you make a good point that this causes some code duplication
>>> (fortunately it's pretty simple logic).  So if you'd like to contribute a
>>> public base class that would be a good API addition.
>>> Cheers,
>>> Pawel
>>> On 05/20/2010 10:40 AM, Mikhail Khodjaiants wrote:
>>>> Hi,
>>>> I am trying to implement a custom content for the Registers view for
>>>> DSF/GDB. As far as I understand, I need to register an adapter factory for
>>>> my ILaunch class. The best way to do it is to extend GdbAdapterFactory, but
>>>> the package that includes it is not exported as well as the commands
>>>> package.
>>>> The only other option is to write my own implementation or copy the
>>>> existing one (with all legal consequences) for all these classes into my
>>>> plug-ins.
>>>> Is this correct or maybe I am missing something?
>>>> And what is the criteria of exporting internal packages?
>>>> Thanks,
>>>> Mikhail
>>>> _______________________________________________
>>>> cdt-dev mailing list
>>>> cdt-dev@xxxxxxxxxxx
>>> _______________________________________________
>>> cdt-dev mailing list
>>> cdt-dev@xxxxxxxxxxx
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

Back to the top