On Thu, Mar 26, 2009 at 2:43 AM, Dianne Hackborn <[email protected]> wrote: > On Wed, Mar 25, 2009 at 4:59 PM, Stoyan Damov <[email protected]> > wrote: >> >> The information I provided (consistent crash address and assembly >> around it) should be sufficient to any skilled Windows C++ developer >> to find the bug in 10 minutes, provided that the appt tool was built >> with Microsoft Visual Studio, or another toolchain, which has the >> equivalent of VS's .map files. > > I am the primary developer of the tool, and the computer I do my development > on is a Mac. I don't have a Windows machine, and have no idea how to build > that tool for windows.
OK, I understand. Who builds the tool for the Windows SDK then? What tools are used to build it? So, is the tool open source, where's the source, and if you could ask who builds the tool for Windows, what tools are used to build it and how is it built? > > If you give me a test case then I can run it on my machine and debug it. > Very likely the place it crashes is not going to tell a whole lot about the > problem (I have enough experience debugging aapt to have been through this), > so being able to reproduce the problem will help me spend a lot less time on > fixing it -- I can turn on debugging logs to identify what is going on, etc. A single empty line between 2 activities in the AndroidManifest.xml make the difference. > > That said, you are acting like you expect someone to drop what they are > doing today to spend all of their time on this bug. I'm sorry, but it isn't > going to happen -- a bug fix for this would be in the next SDK, which means > probably cupcake, so you won't have an SDK with a fix for it until then. Whoa, so if I couldn't workaround the problem I should seize development? Now that's great! > Also we are still focused on development on the device-side parts of Cupcake > (since those need to be ready first for schedules, to be burned on devices > as they are manufactured), so fixes on tools in general will be held up > until we are ready to work on that part. And here we go again with the cupcake thing (a bit off-topic). Schedules were non-existent yesterday, today you're chasing deadlines? Other than that I understand fixing tools is with lesser priority, but at least we need the source code and build instructions so we can fix them and continue our work! > > Finally, if this is really such a critical issue that you can't do anything > else until it is addressed, you -do- have the power to build aapt yourself > and debug it. You aren't reliant on Google to do things for you. That's > the give and take we have here: Google is giving away a bunch of stuff to > the OHA for Android so lots of people can use it for free, but because we > are not being paid for any of this work it is hard to have people who can > drop everything for a problem that a particular developer is having. OK, this answers my previous questions. aapt is open source, and it's somewhere. Now I only need to figure out how to build it. > I -do- want to have this fixed. I won't be able to do it today or probably > even tomorrow. It is also much easier to fix with a test case; without a > test case, I can anticipate spending a lot more time on it (just figuring > out how to get a windows build) so it will naturally be lower on my list of > priorties than other things that I can spend less time on for a bigger > benefit. Understood. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
