<Linking>
>> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\004163, line 66: error:
can't find input file '/lib/evmdm6437bsl.lib'
>> Compilation failure
Build Complete,
2 Errors, 0 Warnings, 0 Remarks.
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.
<Linking>
>> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\004163, line 66: error:
can't find input file '/lib/evmdm6437bsl.lib'
>> Compilation failure
Build Complete,
2 Errors, 0 Warnings, 0 Remarks.
The linker can't find the library. You will need to adjust your linker search paths in the project options. In this case since it looks like library is being included with /lib in front of it you will want add the path up until that point.
For example if the library were in the following folder on my PC: C:\libraries\DM6437\lib\evmdm6437.lib
I would need to add the following to my search path "C:\libraries\DM6437". To be safe I would also add "C:\libraries\DM6437\lib"
Note that this is just an example you will have to use the paths that match where the library is located on your computer.
I've got the simpler demos (e.g. 648 preview) building thanks to a big string of dirs in the XDCPATH env var, & these run, having found the Lyrtech gel for the 648EVB (its only in CCS6!).
I'm almost there with the hostapp demo - I just need to resolve
js: "C:/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/ti/bios/log/support/package.xs", line 25: exception from uncaught JavaScript throw: TypeError: Cannot call method "create" of undefined (C:/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/ti/bios/log/support/package.xs#25)
"C:/dvsdk_1_01_00_15/xdc_2_95_02/packages/xdc/cfg/Main.xs", line 248
The trouble is that this package is already in my path:
ti.bios.log.support.sch is in
C:\dvsdk_1_11_00_00_DM648\biosutils_1_00_02\packages\ti\bios\log\support\package
& I have
\dvsdk_1_11_00_00_DM648\biosutils_1_00_02\packages\;
in my XDCPATH, which in full is:
/dvsdk_1_11_00_00_DM648/examples/common/evmDM6437/;
/dvsdk_1_11_00_00_DM648/biosutils_1_00_02/packages/;
/dvsdk_1_11_00_00_DM648/codec_engine_1_20_02/packages/;
/dvsdk_1_11_00_00_DM648/edma3_lld_1_05_00/packages;
/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/;
/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/fctools/;
/dvsdk_1_11_00_00_DM648/ndk_1_92_00_22_eval/;
/dvsdk_1_11_00_00_DM648/pspdrivers_1_10_00/packages;
/dvsdk_1_11_00_00_DM648/xdais_5_21/;
/dvsdk_1_11_00_00_DM648/xdc_2_95_02/;
/dvsdk_1_11_00_00_DM648/codecs_1_10_evmDM648/packages;
/dvsdk_1_11_00_00_DM648/xdais_5_21/packages;
/dvsdk_1_11_00_00_DM648/framework_components_1_20_03/packages/;
/CCStudio_v3.3/bios_5_31_08/packages/;
There are other packages under
\dvsdk_1_11_00_00_DM648\biosutils_1_00_02\packages\;
e.g. ti.bios.utils.sch
the only thing that I can think of, is that I've tweaked the paths to the header files as I
assimilate the DVSDK, in order to get past all of the compiler preproc errors due to not having the include (-i) paths set up. Now that these are set, perhasp if I unpick my changes, the problem will evaporate.