Greetings,
I have a working video capture -> dei -> loopback -> display OMX chain configured with the DM8168EVM and a custom capture board. I am attempting to do some basic image processing using the VLIB APIs.
I have downloaded and installed the latest version of VLIB to my /ti-ezsdk_dm816x-evm_5_05_02_00/component-sources directory. At the moment I am just trying to successfully build the library into my system without calling any of its functions.
Following the VLIB User Guide, I have inlcuded #include <vlib.h> in my ilclient.c file and provided the path of its "packages" directory to my env.mk file (/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx_05_02_00_48/makerules/env.mk) as follows:
# VLIB
vlib_PATH = $(EXTERNAL_SW_ROOT)/vlib_c674x_3_0_1_0
vlib_INCLUDE = $(vlib_PATH)/packages
However, the last step given is proving to be the source of some confusion, as it requires me to also "provide a path to the linker via the -l directive." How should I go about doing this? I have tried linking the library by including the line $(vlib_PATH)/packages/ti/vlib/lib/vlib.ae674 to the "EXTLIBS_c6xdsp =" definition in the dm81xx makefile (/ti-ezsdk_dm816x-evm_5_05_02_00/component-sources/omx_05_02_00_48/examples/ti/omx/demos/dm81xx/makefile), but it only generates an error when I execute "make omx".
If anyone with experience of using VLIB or another integrated library with the EZSDK could weigh in, that would be great.
Thanks,
Marcus
