Yeah, I had seen the basic help that but still had path problems. I eventually got dx to run on the command line and it died with error 2 claiming that it had run out of Java heap space. HOWEVER, I must remind any reader who would leap to a premature conclusion about granting the Java JVM more space that my project builds perfectly fine under the old 1.1_r1 SDK so I seriously doubt a heap space problem is the explanation for why dx fails when run through Eclipse. It is more likely that I am seeing error 2 through Eclipse for a mysterious undescribed reason and am seeing error 2 on the command line for a heap space related problem due to some difference in the way Java is being invoked in the two environments (Eclipse vs. command line).
Furthermore, I gave Java more heap space through Eclipse in the Pref- >Java->Installed JREs->Default VM arguments and the dalvik error 2 problem didn't go away when run through Eclipse (recall that in Eclipse's case I can't actually *see* the dalvik error, so I don't know if the failure is heap space related at all). I am unsure how to grant Java more heap space when I run dx on the command line, so I don't know how to perform that experiment. I know how to give java more space directly, ala -Xms and -Xmx, but not when I run dx as an executable. I think I found the JVM VM heap settings (I'm on a Mac), and upped the heap, and it still die with a heap space error, so maybe I did it wrong. Can I get dx (or the JVM) to show me how much heap space it is using when it runs so I can verify that dx is working with a large heap? At the current time, I remain confused as to the cause of or solution to my problem. Vexation continues. On May 12, 11:20 am, Dan Bornstein <[email protected]> wrote: > On May 11, 6:14 pm, Keith Wiley <[email protected]> wrote: > > > > > On May 11, 5:58 pm, Dan Bornstein <[email protected]> wrote: > > > How are you invoking it? From the commandline, dx should emit a > > > Eclipse does it all automatically when it builds. > > > > description of any problem to the console. From the Eclipse plugin, it > > > should emit it to wherever-it-is-that-Eclipse-puts-error-messages > > > (sorry, I don't use Eclipse myself). > > > Hmmm, the only error I see is in the console and that's just a report > > that it's type 2. For example, Eclipse has an error log window, which > > is totally blank. > > > > Exit code 2 corresponds to an "unexpected top-level exception," > > > meaning it's an error that doesn't have a human-translated > > > explanation, but it should come with at least a "programmer-oriented" > > > message and a stack trace. > > > Where can I find documentation on runing the dalvik convert explicitly > > on the command line so I can see the error message? > > dx has a modicum of self-documentation ("dx --help" or just with no > args). What you want to do is something like: > > dx --debug --dex --output-to=classes.dex path/to/Name.class path/ > to/lib.jar > > where you of course replace the names of classes and jars with > whatever it is you're actually building. The "--debug" argument forces > dx to be verbose in error reporting in cases it otherwise wouldn't be. > Since you say Eclipse isn't showing you an error, it might be that dx > is mistakenly swallowing an error it should be more proactive about > reporting (wouldn't be the first time). > > -dan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
