• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 387 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.

Trying to Build Decode Demo in OMX folder

_Ralph_
Guru 10685 points

Fresh from failing to build the OMTB, I'm also looking at building the decode demo that's in the omx folder within the EZSDK.

I've edited loads of makefiles to ensure they have the right paths in including:

$(ROOTDIR)/makerules/build_config.mk
$(ROOTDIR)/makerules/env.mk
$(ROOTDIR)/component.mk
$(ROOTDIR)/makerules/platform.mk

where ROOTDIR is <EZSDK>/omx_05_01_01_80/packages.

On typing "make" I get a problem that is ultimately caused by the "CORE" environment variable not having been set. What should I set this to? There is no documentation on this or indication what it should be. Please understand that I am a newbie to OMX & H264 in this environment.

I know that the possibilities are:

  • m3vpss
  • m3video
  • a8host

I'm going to try all of them and see what happens but I'd appreciate some proper firm advice on how to proceed; I have no idea what to do with the binary that results from this build process. I feel like I'm blindly fumbling along an unknown path, trying different things until they work. It shouldn't have to be this hard.

Thanks,

Ralph

  • 0
    Guru 10685 points

    Sort of solved. The decode demo is built as part of the overall "make" or "make omx" which you run in the root of the EZSDK (in which case you don't have to edit any more makefiles as I did). I never got the m3 builds to work as the makefiles seemed to be incomplete however I got the a8host target to build and it ended up in the bin folder.

    When you type "make" in the root of the EZSDK you find the binary is placed in "omx_05_01_01_80/prebuilt-binaries/decode/bin/ti816x-evm/" instead.

    Obviously it would have been nice if the Software Developer's Guide mentioned all this rather me having to spend a day on it.

    Ralph