• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 258 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Building DVSDK drivers (CMEM, DSPLINK) and other objects locally ("out-of-tree") in user's home area, with local settings

Mike Whittaker
Intellectual 410 points

Sorry if this is covered somewhere in the docs, but all the examples I see regarding building the drivers, codec engine etc.  just do so in-place within the SDK installation directories.

host $ cd $(DVSDK)
host $ make codecs_clean
host $ make codecs

Is there a recommended way to set up and build with the drivers source so that different users (or just different products which need their own settings) on a system with DVSDK installed, can work with their own local source copies ?  Or should one just copy the relevant directories ?

eg working in /home/users/joe_bloggs/dvsdk_drivers/cmem  ... dvsdk_drivers/dsplink

This is really to allow builds to be done with different build settings, so if a local make with suitable parameters could still use all the in-place DVSDK source files, but just generate its build output(s) locally (and use local parameter files), that would be very useful.

  • 0
    TI__Mastermind 18260 points

    Mike Whittaker said:

    eg working in /home/users/joe_bloggs/dvsdk_drivers/cmem  ... dvsdk_drivers/dsplink

    This is really to allow builds to be done with different build settings, so if a local make with suitable parameters could still use all the in-place DVSDK source files, but just generate its build output(s) locally (and use local parameter files), that would be very useful.

    Mike,

    Each subcomponent of the DVSDK comes packaged with its own build framework, so there's no "one-stop-shopping" for doing what you want to do, and there is likely no built-in support for it in some of the subcomponents.

    For instance, CMEM's Makefile framework doesn't have any facility to direct the output of build stages to a different location.  While you can "install" the ultimate generated file (e.g., cmemk.ko from cmem/src/module) into a directory specified through $(EXEC_DIR), the intermediate files get built "in-place".

    I would say your easiest solution is to just copy the sources and build framework files to a separate location.

    Regards,

    - Rob