Wind River Support Network

Description

Follow the steps to build ti-img-rogue-driver:

  1) set BB_NO_NETWORK as '0' in <path-of-project>/build/conf/local.conf file.

  2) Launch bitbake to build an image with graphics support

     $ cd path_to_your_project
     $ . ./environment-setup-x86_64-wrlinuxsdk-linux
     $ . ./oe-init-build-env
     $ cat << _EOF >> conf/local.conf
DISTRO ?= "wrlinux-graphics"
MACHINE_FEATURES += " gpu"
CUSTOMER_RECIPES:wr-ti-j72xx += 'img-pvr-sdk'
CUSTOMER_RECIPES:meta-ti-bsp += 'ti-img-rogue-umlibs'
_EOF
     $ bitbake ti-img-rogue-driver

Build failed.

Steps to Reproduce

1. git clone --branch WRLINUX_10_22_LTS https://gateway.delivers.usa.windriver.com/git/linux-lts/release/wrlinux-lts.22/WRLinux-lts-22-Core/wrlinux-x
2. ./wrlinux-x/setup.sh --machines ti-j72xx --dl-layers
3. edit local.conf file with network enabled
4.add in local conf:

*1st config*

MACHINE_FEATURES +=" gpu"
CUSTOMER_RECIPES:wr-ti-j72xx += 'img-pvr-sdk'
CUSTOMER_RECIPES:meta-ti-bsp += 'ti-img-rogue-umlibs'

bitbake ti-img-rogue-driver

*2nd config*

CUSTOMER_RECIPES:wr-ti-j72xx += 'img-pvr-sdk ti-img-rogue-driver'
CUSTOMER_RECIPES:meta-ti-bsp += 'ti-img-rogue-umlibs'

bitbake ti-img-rogue-driver

*3rd config*

CUSTOMER_RECIPES:wr-ti-j72xx += 'img-pvr-sdk ti-img-rogue-driver'
CUSTOMER_RECIPES:wr-ti-j72xx += 'ti-img-rogue-umlibs'

bitbake ti-img-rogue-driver

*4th config (reference config from BSP README)*

DISTRO ?= "wrlinux-graphics"
MACHINE_FEATURES += " gpu"
CUSTOMER_RECIPES:wr-ti-j72xx += 'img-pvr-sdk'
CUSTOMER_RECIPES:meta-ti-bsp += 'ti-img-rogue-umlibs'

bitbake wrlinux-image-std-sato

First three configuration fails due to fetching issues of bitbake ti-img-rogue-driver. Last one due to a missing dependency ti-img-rogue-umlibs-dev.