|Re: [cdt-dev] how to keep backward compatibility for launch file when switch from CDI to DSF|
So you want to automatically migrate CDI-GDB laugh configurations to DSF-GDB ones?
We haven't done that in CDT. But the two types of launch configurations are very similar, so it shouldn't be too hard. In fact, in simple cases, it may not really need any conversion.
What I would do is look through the different tabs of the DSF-GDB launch configuration type in question, and look for the constants used to store the info for a launch config. Then look to see if CDI used the same ID. If not, you'll have to convert from the old ID to the new one.
We are developing our DSF debugger plugins to replace our CDI based plugins. the issue is how to support our customer’s old workspace that contains CDI based launch files?
How DSF-GDB solve this backward compatibility issue over CDI-GDB on the before? What’s the eclipse bug number for this? Thanks in advance.
Back to the top