Failed to build Android with TI DSP stack
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1.make TARGET_PRODUCT=beagleboard BUILD_WITH_GST=true dvsdk
2.
3.
What is the expected output? What do you see instead?
Build should be finished successfully. But it failed with an error message
"..../external/ti-dsp/dvsdk_3_00_02_44/cg6x/bin/cl6x: not found" while
compiling the failure.c file.
What version of the product are you using? On what operating system?
I'm using beagleboard C3 and compiling the suit on ubuntu 8.04.
Please provide any additional information below.
I have tried two ways to compile the suit but each way failed at the same
place:
1): Put pre-downloaded DVSDK under the external/ti-dsp folder. And check
out the TIGStreamerPlugins using the command line:
# svn checkout -r 506 --username anonymous --password "" -q
https://gstreamer.ti.com/svn/gstreamer_ti/trunk/gstreamer_ti
The DVSDK includes dvsdk_setuplinux_3_00_02_44.bin,
cs1omap3530_setuplinux_1_00_01-44.bin, xdctools_setuplinux_3_15_01_59.bin,
bios_setuplinux_5_33_06.bin, TI-C6x-CGT-v6.0.16.1.bin
Then use the following command to build the suit:
make TARGET_PRODUCT=[omap3evm | beagleboard] BUILD_WITH_GST=true dvsdk
2): Remove the above DVSDK files from the external/ti-dsp folder and
directly type the following command:
make TARGET_PRODUCT=[omap3evm | beagleboard] BUILD_WITH_GST=true dvsdk
It does automatically download DVSDK and TIGStremear Plugins then start
building, but fails when while compiling the failure.c file.
```
Original issue reported on code.google.com by `shermanhng@gmail.com` on 20 Dec 2009 at 7:58
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing `make TARGET_PRODUCT=beagleboard BUILD_WITH_GST=true dvsdk` and inspect the failure while compiling `failure.c`. Check the referenced `external/ti-dsp/dvsdk_3_00_02_44/cg6x/bin/cl6x` path and the listed DVSDK setup files. Done means the Android DVSDK build completes without the `cl6x: not found` error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- build-system, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100