search

ATLFlight / cmake_hexagon

CMake toolchain and rules for building apps for Hexagon DSP and apps processor on Qualcomm SoCs
29 stars 56 forks source link

bundle.cmake: What happens to APPS_LINK_LIBS? #18

Open han-so1omon opened 7 years ago

han-so1omon commented 7 years ago

The apps link libs aren't passed to the custom_target in bundle.cmake as far as I can tell. My evidence for this is that the string 'APPS_LINK_LIBS' appears once in the bundle.cmake file (in the set(multiValueArgs) function). This differs from the LINUX_LIB and LINUX_APP functions in the linux_app.cmake, which do link the link libs with the app. As such, I don't think that I can simply link a library with the linux app using QURT_BUNDLE().

han-so1omon commented 7 years ago

The Linux and QURT side apps compile and link when using the alternative method of compiling each side individually. The discrepancy may have to do with the lack of a CMake Toolchain specified for the Linux-side under the Makefile paradigm specified in the helloworld example.

mcharleb commented 7 years ago

@han-so1omon The typical use with bundle was to make a DSP lib (that is really a DSP app) that only needed a simple ARM app to invoke it. This is likely an oversight because not bundle target ever required additional libs for the ARM target. I will have a look.