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
-~----------~----~----~----~------~----~------~--~---
