Hi folks,

Great ! Vertical plugins will be very appreciated !!!

After checking the code/doc, I would like to point 2 things :

- I'm afraid that obex part of the code is not compliant with multi-user architecture. We need a separate "obex-service" (in bluetooth-frwk-NG) daemon discussing with obexd daemon across org.bluez.obex d-bus service.

- In current bluetooth-frwk, there are vconf keys checked related to bluetooth. I suppose they are not integrated yet... or may it has to be used in specific verticals...

Thanks and regards,
Corentin


On 01/11/2014 02:43 AM, Xu, Martin wrote:
Hi:
Please allow me to announce the 0.2 release of Bluetooth-Frwk-NG(Bluetooth Framework New 
Generation) on behalf of "Tizen Connectivity and network work stream".  It is 
the first release on Tizen.org. The work stream want to redesign and implement Bluetooth 
Framework for Tizen-3.0 and make it more efficient, extensible, and easy to maintain and 
port to other platforms. So we decide to kick off the project at tizen.org. Before the 
mature of the project, the old Bluetooth-frwk project will coexist with Bluetooth-frwk-ng.

Bluetooth-frwk-NG project maintain and develop at tizen 
gerrit/platform/core/connectivity/bluetooth-frwk devel branch
Bluetooth-frwk project still maintain at tizen branch.

I want to thank Steve, Pyun and Samsung connectivity team, Andrei, Johan and 
Intel comms upstream team; Thanks Zheng, Wu and JiangBo's great efforts on it.

==Bluetooth-Frwk-NG release Notes==

--Bluetooth-Frwk-NG overview

Bluetooth-Frwk-NG (Tizen Bleutooth Framework New Generation) provides Bluetooth 
CAPI(Core API) for
Tizen Applications. Most of the CAPI calls to BlueZ directly, only limited 
BlueZ events will be monitored
by Bluetooth-Frwk-NG daemon called Bluetoth-service deadmon. The vertical 
plugin is designed to handle the
vertical/plaftorm specific operation to make it easy to port to other platforms 
and verticals.BlueZ lib
handles the BlueZ operations and make blueZ integration more easily. "Develop mode" 
and "target
mode" is implemented to facilitate developing work. Most of the work can be 
done at develop mode on linux PC.

"Develop mode" can be run on linux PC(Ubuntu, fedra and other linux 
distribution). It is used for most of the
developing and testing work. The test applications are used facilitate the 
development work.
    Bluetooth-Frwk-NG/test/bluez-capi-test: used to test the Bluetooth CAPI
    Bluetooth-Frwk-NG/test/bluez-lib-test: used to test BlueZ lib for Bluetoothd
    Bluetooth-Frwk-NG/test/obex-lib-test: used to test BlueZ lib for Obexd
    Bluetooth-Frwk-NG/test/bt-serivce-lib-test: used to test bluetooth service 
lib


"Target mode" should run on the target machine(like IA mobile phone and Samsung 
phone) running with the Tizen
environment. The final testing and tunning integration work should use target 
mode and make sure the applications
and Bleutooth-Frwk-NG itself running perfectly at target Tizen machine.


--Compiling and install Bluetooth-Frwk-NG

You can compile Bleutooth-Frwk-NG on linux PC.

1.Download Bluetooth-Frwk-NG from Tizen.org
    git clone 
[email protected]/gerrit/platform/core/connectivity/bluetooth-frwk
    git checkout -b devel remotes/origin/devel
    to switch to devel branch, currently, Bluetooth-frwk-NG located at devel 
branch of Bluetooth-frwk project.

2. Make sure below tools and library are installed on linux PC.
    - CMake tool
    - GCC compiler
    - D-Bus library
    - glib-2.0 library
    - gio-2.0 library
    - gio-unix-2.0 library

3. Compile Bluetooth-Frwk-NG.
    a. cd bluetooth-frwk
    b. cmake . && make
    currently, Bluetooth-Frwk-NG support IA default. Please modify the related 
files of cmake to support ARM
    welcome patches to make it more elegant.

4. Install on develop machine the linux PC (for develop mode)
    a. sudo cp packaging/bluetooth-service.conf
              packaging/bluezlib.conf
               packaging/bluez-lib-test.conf
               packaging/bluezobex.conf
               /etc/dbus-1/system.d/
    b. make install
    notes: also welcome the patches to make it elegantly.

5. Install on target machine (for target mode)
   a. cp packaging/bluetooth-service.conf
         packaging/bluezlib.conf
         packaging/bluez-lib-test.conf
         packaging/bluezobex.conf to /etc/dbus-1/system.d/ of target machine
   b. cp ./src/bluetooth-service
         ./test/bluez-capi-test
         ./test/bluez-lib-test
         ./test/obex-lib-test
         ./test/bt-serivce-lib-test to running dir (such as /usr/local/bin) of 
target machine
   c. cp ./capi/libcapi-network-bluetooth.so* to /usr/lib/ of target machine
   d. cp ./include/bluetooth.h to /usr/local/include/network/bluetooth.h of 
target machine
   e. cp ./capi-network-bluetooth.pc to /usr/lib/pkgchonfig of target machine

   notes: we will create the RPM package for bluetoth-Frwk-NG to make it more 
easy to install on target machine

--Running Bluetooth-Frwk-NG
1. run & test Bluetooth-Frwk-NG on linux PC(Develop mode)
    a. cd bluetooth-frwk
    b. after compiling, bluetooth-service exists in in the dir of src/
       "bluetooth-service" is the Bluetooth-Frwk-NG daemon.
    c. run "bluetooth-service"
    d. cd bluetooth-frwk
    e. after compiling, Bluetooth-Frwk-NG test programs exist in in the dir of 
test/
       ./test/bluez-capi-test is used to test Bluetooth-Frwk-NG CAPI interfacdes
       ./test/bluez-lib-test is used to test Bluetooth-Frwk-NG access Bluez 
directly interfaces
       ./test/obex-lib-test is used to test Bluetooth-Frwk-NG access obex 
directly interfaces
       ./test/bt-serivce-lib-test is used to test Bluetooth-Frwk-NG service 
daemon interfaces
       notes: type connmand "h" for detail

2. run & test Bluetooth-Frwk-NG on target Machine(Target mode)
    a. enter running dir (such as /usr/local/bin) of target machine
    b. run "bluetooth-service"
    c. for different test target, run ./test/bluez-capi-test or
                                      ./test/bluez-lib-test
                                      ./test/obex-lib-test
                                      ./test/bt-serivce-lib-test

--how to submit patch to the project.
    1.cd bluetooth-frwk
    2.modify the related files
    3.git add the related files
    4.git commit
    5.git push origin HEAD:refs/for/devel
       The patch will be submitted to gerrit of tizen.org.
    6.in the patch of review.tizen.org/gerrit/, the developer need to add the 
related persons to review.
    Notes: We use Tizen gerrit developing process to submit patches and 
maintain the project. Please refer
    tizen.org for detail.

--How to develop apps using Bleutooth-Frmk-NG
    Tizen Bluetooth apps are based on Bluetooth CAPIs provided by 
Bleutooth-Frmk-NG.

    Please refer ./inlcude/bluetooth.h for BT CAPIs.

    We try to keep compatible with Tizen CAPI. But some modifications to CAPI 
still can't avoid. We will try to push the modification
    of the CAPI to Tizen.


_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to