Skip to content

Commit 4aa1327

Browse files
jsuhaas22cshilwant
authored andcommitted
feat: linux: Add compilation instructions for TI Apps Launcher
meta-arago-toolchain lacks Qt6 support for compiling TI Apps Launcher. The correct way to compile it is to use Yocto. However, for quicker way to compile it, we can also use ARM64 Docker containers. Provide a guide on how to compile ti-apps-launcher using ARM64 Docker container which TI provides [0]. [0] https://github.com/TexasInstruments/ti-docker-images/pkgs/container/debian-arm64 Signed-off-by: Suhaas Joshi <s-joshi@ti.com>
1 parent 8325481 commit 4aa1327

1 file changed

Lines changed: 60 additions & 0 deletions

File tree

source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst

Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -438,3 +438,63 @@ Power Menu
438438
.. Image:: /images/ti-apps-launcher-powermenu2.png
439439
:height: 400
440440

441+
Compiling TI Apps Launcher
442+
--------------------------
443+
444+
The ideal way to compile TI Apps Launcher is to trigger a Yocto
445+
build. But for a quicker way to do it, especially during development,
446+
TI provides a `debian-arm64
447+
<https://github.com/TexasInstruments/ti-docker-images/pkgs/container/debian-arm64>`__
448+
Docker image. This image already has all dependencies required
449+
for compiling ti-apps-launcher.
450+
451+
First, clone TI Apps Launcher on host:
452+
453+
.. code:: console
454+
455+
git clone https://github.com/texasinstruments/ti-apps-launcher.git
456+
export TI_APPS_LAUNCHER_REPO="$(pwd)/ti-apps-launcher"
457+
cd ti-apps-launcher
458+
459+
Then, add the following line in :file:`CMakeLists.txt`:
460+
461+
.. code:: console
462+
463+
add_compile_definitions(SOC_AM62=1) # if target is AM62x or AM62SIP
464+
add_compile_definitions(SOC_AM62_LP=1) # if target is AM62x-LP
465+
add_compile_definitions(SOC_AM62P=1) # if target is AM62P
466+
467+
Then, pull TI's debian-arm64 Docker image and run it:
468+
469+
.. code:: console
470+
471+
docker pull ghcr.io/texasinstruments/debian-arm64:latest
472+
docker run -it -v ${TI_APPS_LAUNCHER_REPO}:/root/ti-apps-launcher ghcr.io/texasinstruments/debian-arm64 bash
473+
474+
Finally, run:
475+
476+
.. code:: console
477+
478+
cmake -B build -S . -DRT_BUILD=0 # if target is RT image, make -DRT_BUILD=1
479+
make -C build
480+
481+
The compiled binary should be :file:`build/ti-apps-launcher`.
482+
483+
Copy the compiled binary to :file:`/usr/bin/` directory of the target:
484+
485+
.. code:: console
486+
487+
scp ${TI_APPS_LAUNCHER_REPO}/build/ti-apps-launcher root@<ip-addr-of-device>:/usr/bin
488+
489+
If you have modified the scripts in the :file:`scripts/` directory, then copy them too:
490+
491+
.. code:: console
492+
493+
scp -r ${TI_APPS_LAUNCHER_REPO}/scripts root@<ip-addr-of-device>:/opt/ti-apps-launcher
494+
495+
.. note::
496+
497+
This is a quick and easy way to compile ti-apps-launcher during
498+
development, but it is a good idea to validate with Yocto builds
499+
often. There is a possibility that compiler mismatch could present
500+
issues in the run up to production.

0 commit comments

Comments
 (0)