Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] CDT for Windows, launching, and Wascana

I feel like I'm missing something. Last time I checked, I created a C project, built it, hit the debug button,, I was in the debugger with the program stopped at the main() of my program. The only snag was the lack of source with Cygwin, but obviously that's not an issue for Wascana.

This hassle-free workflow was made possible by the context-sensitive launch logic that you and Darin worked on. So, what am I missing? Where is the opportunity for improvement? The only thing I can think of is the fact that gdb had to be in the PATH, but Doug is apparently already focused on addressing that.


At 05:02 PM 4/16/2010, ken.ryall@xxxxxxxxx wrote:
Content-Language: en-US
Content-Type: multipart/alternative;


In the next couple weeks I want to start looking at the out of the box launch experience for someone who downloads CDT for Windows.

There has been some discussion about this and a few relevant bugs but I'd like to step back and look at it fresh from start to finish.

So my first question is, what's the status of Wascana? I'm planning to skip over the issue of how people who download CDT for Windows get Wascana, assuming we'll tackle that separately. So since it sounds like you have been doing some new work on Wascana I wanted to see if there is there a new update site I can pull it from?

Thanks - Ken
cdt-dev mailing list

Back to the top