CSS4 VLIB linking problem

Csaba,

You get the unresolved symbol error when you are calling a function but it is not defined in your executable, i.e. the linker can't resolve it.  The problem is likely a missing library that needs to be included.  However I have no experience using the Video Analytics & Vision Library so I can't point you to which specific library file is missing. 

I am going to move the post back into the DaVinci forum now so that the team there can help with the VLIB questions.

Regards,

John

JohnS,

I know what "unresolved symbol" mean.

I hope I'm wrong, but I'm afraid it's a bug.

The VLIB package consists a header a file (VLIB_prototypes.h) and a library binary file compiled by TI (vlib.l64p).

VLIB_updateEWRMeanS32() is a VLIB library function. It should be in the vlib.l64p, but the linker doesn't find it.

As you can see the linker command line, the vlib.l64p library is added to the project.

I watched the vlib.l64p file by a text editor: the symbol exists in the file.

I guess it can be a version incompatibility issue, because the vlib is tested by CSS3.3 regarding its readme file.

Thanks,

Csaba

Csaba,

I tried to replicate your behaviour by adding the following code to some existing CCS v4 code I had that.

{

int * currentMean;

unsigned char * newestData;

unsigned int * foreground;

VLIB_updateEWRMeanS32(currentMean, newestData,foreground, numInBytes,numInBytes);

}

and then built it with following output

'Invoking: Compiler'

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 6.1.16/bin/cl6x" -mv64+ -g --define=CHIP_DM6437 --define=DO_NOT_USE_CODEC_ENGINE --define=SIMULATOR --define=_NTSC --define=DM6437_SOC_BUILD --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 6.1.16/include" --include_path="C:/CCStudio_v3.3/c6400/VLIB_V_2_1/include" --include_path="C:/CCStudio_v3.3/boards/evmdm6437_v2/include" --diag_warning=225 --preproc_with_compile --preproc_dependency="video_universal_app_empty.pp" --cmd_file="C:/dvsdk_1_11_00_00_universal_codecs_ccs_v4/examples/video_universal_app_empty_no_ce_configuration/Default/configPkg/compiler.opt" "C:/dvsdk_1_11_00_00_universal_codecs_source/examples/video_universal_app_empty/evmDM6437/video_universal_app_empty.c"

'Finished building: C:/dvsdk_1_11_00_00_universal_codecs_source/examples/video_universal_app_empty/evmDM6437/video_universal_app_empty.c'

' '

'Building target: video_universal_app_empty_no_ce.out'

'Invoking: Linker'

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 6.1.16/bin/cl6x" -@ccsLinker.opt -o "video_universal_app_empty_no_ce.out"

<Linking>

'Finished building target: video_universal_app_empty_no_ce.out'

' '

So I'd conclude that there is nothing intrinsically wrong with the vlib.l64p library in VLib 2.1. Suggestions I would make are:

- check linker search paths are correct and that you have no other vlib.l64p libs on your system that may be picked up by mistake

- cut and paste the CCS build output to a DOS patch file and then see how that links outside CCS. Ideally strip it back to as simple a system as possible.

Iain