... | @@ -73,9 +73,7 @@ sudo hciconfig hci0 piscan && hciconfig |
... | @@ -73,9 +73,7 @@ sudo hciconfig hci0 piscan && hciconfig |
|
At this point of time it doesn't seem to be possible to only use the BlueCove library by only by only including the dependency. The problem that couldn't be solved in this case is an ``osgi.wiring`` problem for embedding the functionallity of ``com.ibm.oti.connection`` to the bundles build via the pom-files embedded dependencies. This would be the usual way, but as mentioned, it couldn't be solved right now.
|
|
At this point of time it doesn't seem to be possible to only use the BlueCove library by only by only including the dependency. The problem that couldn't be solved in this case is an ``osgi.wiring`` problem for embedding the functionallity of ``com.ibm.oti.connection`` to the bundles build via the pom-files embedded dependencies. This would be the usual way, but as mentioned, it couldn't be solved right now.
|
|
|
|
|
|
### Using BlueCove Code
|
|
### Using BlueCove Code
|
|
To solve this problem, the code from ``bluecove-gpl-2.1.1-SNAPSHOT`` has been downloaded and the packages ``javax`` and ``com`` have been added to the code. The code then through some exceptions while loading the native code file ``libbluecove_arm.so``. Therefore the path for this native code is set hardcoded (for now) as follows:
|
|
To solve this problem, the code from ``bluecove-gpl-2.1.1-SNAPSHOT`` has been downloaded and the packages ``javax`` and ``com`` have been added to the code. The code then through some exceptions while loading the native code file ``libbluecove_arm.so``. Therefore the path for this native code is set hardcoded.
|
|
|
|
|
|

|
|
|
|
|
|
|
|
That obvioselly means that this directory has to include this file to make the Bundle runnable without errors.
|
|
That obvioselly means that this directory has to include this file to make the Bundle runnable without errors.
|
|
|
|
|
... | | ... | |