2012-10-16 3 views
0

나는 complied hello-jni 예제 인 am 명령을 사용하여 adb 쉘에서 시험해 봅니다. hello-jni가 성공적으로 컴파일되었습니다.android sdk/ndk 활동 관리자가 hello-jni 예제를 실행하지 못했습니다.

[email protected]_win7 /cygdrive/d/dev/NDK/android-ndk-r8b-windows/android-ndk-r8b/samples/hello-jni 
$ adb shell 
[email protected]:/ $ am start -a android.intent.action.MAIN -n com.example.hellojni com.example.hellojni.HelloJni 

을이 오류 메신저가 점점 :

[email protected]:/ $ am start -a android.intent.action.MAIN -n com.example.hellojni com.example.hellojni.HelloJni 
ion.MAIN -n com.example.hellojni com.example.hellojni.HelloJni    < 
usage: am [subcommand] [options] 
usage: am start [-D] [-W] [-P <FILE>] [--start-profiler <FILE>] 
       [--R COUNT] [-S] <INTENT> 
     am startservice <INTENT> 
     am force-stop <PACKAGE> 
     am kill <PACKAGE> 
     am kill-all 
     am broadcast <INTENT> 
     am instrument [-r] [-e <NAME> <VALUE>] [-p <FILE>] [-w] 
       [--no-window-animation] <COMPONENT> 
     am profile [looper] start <PROCESS> <FILE> 
     am profile [looper] stop [<PROCESS>] 
     am dumpheap [flags] <PROCESS> <FILE> 
     am set-debug-app [-w] [--persistent] <PACKAGE> 
     am clear-debug-app 
     am monitor [--gdb <port>] 
     am screen-compat [on|off] <PACKAGE> 
     am display-size [reset|MxN] 
     am to-uri [INTENT] 
     am to-intent-uri [INTENT] 

am start: start an Activity. Options are: 
    -D: enable debugging 
    -W: wait for launch to complete 
    --start-profiler <FILE>: start profiler and send results to <FILE> 
    -P <FILE>: like above, but profiling stops when app goes idle 
    -R: repeat the activity launch <COUNT> times. Prior to each repeat, 
     the top activity will be finished. 
    -S: force stop the target app before starting the activity 

am startservice: start a Service. 

am force-stop: force stop everything associated with <PACKAGE>. 

am kill: Kill all processes associated with <PACKAGE>. Only kills. 
    processes that are safe to kill -- that is, will not impact the user 
    experience. 

am kill-all: Kill all background processes. 

am broadcast: send a broadcast Intent. 

am instrument: start an Instrumentation. Typically this target <COMPONENT> 
    is the form <TEST_PACKAGE>/<RUNNER_CLASS>. Options are: 
    -r: print raw results (otherwise decode REPORT_KEY_STREAMRESULT). Use with 
     [-e perf true] to generate raw output for performance measurements. 
    -e <NAME> <VALUE>: set argument <NAME> to <VALUE>. For test runners a 
     common form is [-e <testrunner_flag> <value>[,<value>...]]. 
    -p <FILE>: write profiling data to <FILE> 
    -w: wait for instrumentation to finish before returning. Required for 
     test runners. 
    --no-window-animation: turn off window animations will running. 

am profile: start and stop profiler on a process. 

am dumpheap: dump the heap of a process. Options are: 
    -n: dump native heap instead of managed heap 

am set-debug-app: set application <PACKAGE> to debug. Options are: 
    -w: wait for debugger when application starts 
    --persistent: retain this value 

am clear-debug-app: clear the previously set-debug-app. 

am monitor: start monitoring for crashes or ANRs. 
    --gdb: start gdbserv on the given port at crash/ANR 

am screen-compat: control screen compatibility mode of <PACKAGE>. 

am display-size: override display size. 

am to-uri: print the given Intent specification as a URI. 

am to-intent-uri: print the given Intent specification as an intent: URI. 

<INTENT> specifications include these flags and arguments: 
    [-a <ACTION>] [-d <DATA_URI>] [-t <MIME_TYPE>] 
    [-c <CATEGORY> [-c <CATEGORY>] ...] 
    [-e|--es <EXTRA_KEY> <EXTRA_STRING_VALUE> ...] 
    [--esn <EXTRA_KEY> ...] 
    [--ez <EXTRA_KEY> <EXTRA_BOOLEAN_VALUE> ...] 
    [--ei <EXTRA_KEY> <EXTRA_INT_VALUE> ...] 
    [--el <EXTRA_KEY> <EXTRA_LONG_VALUE> ...] 
    [--eu <EXTRA_KEY> <EXTRA_URI_VALUE> ...] 
    [--eia <EXTRA_KEY> <EXTRA_INT_VALUE>[,<EXTRA_INT_VALUE...]] 
    [--ela <EXTRA_KEY> <EXTRA_LONG_VALUE>[,<EXTRA_LONG_VALUE...]] 
    [-n <COMPONENT>] [-f <FLAGS>] 
    [--grant-read-uri-permission] [--grant-write-uri-permission] 
    [--debug-log-resolution] [--exclude-stopped-packages] 
    [--include-stopped-packages] 
    [--activity-brought-to-front] [--activity-clear-top] 
    [--activity-clear-when-task-reset] [--activity-exclude-from-recents] 
    [--activity-launched-from-history] [--activity-multiple-task] 
    [--activity-no-animation] [--activity-no-history] 
    [--activity-no-user-action] [--activity-previous-is-top] 
    [--activity-reorder-to-front] [--activity-reset-task-if-needed] 
    [--activity-single-top] [--activity-clear-task] 
    [--activity-task-on-home] 
    [--receiver-registered-only] [--receiver-replace-pending] 
    [--selector] 
    [<URI> | <PACKAGE> | <COMPONENT>] 

Error: Bad component name: com.example.hellojni 

난 이유를 이해 해달라고 내가 안녕하세요 - JNI 디렉토리 아래에서 무엇을 이 무엇입니까? 어떤 생각?

답변

1

매니페스트 파일에서 하나 schould -n ApplicationPackage/MainActivityClass, ApplicationPackage를 사용하려고

adb shell am start -n com.toto.tests/com.toto.tests.MainActivity 
관련 문제