[
https://issues.apache.org/jira/browse/CB-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492836#comment-13492836
]
Tim Kim commented on CB-1678:
-----------------------------
More updates!
I'm pretty close on finishing this. There's only a few rough edges left, but it
is mostly functionally complete.
In any case, here's a short guide to compile example plugin and get it working:
0) Clone this repo/branch:
https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-blackberry-webworks.git;a=shortlog;h=refs/heads/bb10_ext_qnx
1) Download and install the bb10 native sdk:
http://developer.blackberry.com/native/beta/
2) cd into the cordova blackberry webworks repo
3) cd into the framework/ext-qnx
4) Find the bb10 native sdk directory and run "source
bb10_native_sdk_dir/bbndk-env.sh"
5) hit "make"
6) An *.so file will be generated in the nto/arm/so.le-v7/ - copy and rename
this file to echoJNext.so and place it
in the cordova.echo/device folder
7) Use "ant dist" in the cordova blackberry webworks repo to create a new
project with the echo plugin
8) Modify project settings and deploy to device
9) Using the remote web-inspector, call these javascript commands:
var message = { 'message' : "hello"}
win = function(result){ alert(result == "hello") }
fail = function(){ alert('failed') }
cordova.echo.doEcho(message,win,fail)
> Create native extensions for bb10
> ---------------------------------
>
> Key: CB-1678
> URL: https://issues.apache.org/jira/browse/CB-1678
> Project: Apache Cordova
> Issue Type: Bug
> Components: BlackBerry
> Affects Versions: 2.2.0
> Environment: blackberry 10
> Reporter: Tim Kim
> Assignee: Tim Kim
> Fix For: 2.3.0
>
>
> Currently with the webworks blackberry repo, there is no possibility to make
> a native extension for bb10 (this is because bb10 is now qnx with a c++
> implementation). By making the infrastructure to support this, a developer
> would then be able to make their own plugins on the bb10 platform.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
