Part Number: AM5728
Good morning folks,
With a Linux build host and SYS/BIOS 6.46.5.55 I can use CCS7.2.0 to create a new C66xx SYS/BIOS project ('typical' template) for the IDK_AM572x platform that builds OK with the TI v8.1.3 compiler. When I add a one-line include for dsplib (#include <ti/dsplib/dsplib.h>) to main.c then main.c no longer compiles, complaining about a header not being found:
>> Compilation failure
subdir_rules.mk:21: recipe for target 'main.obj' failed
"/home/keith/ti/dsplib_c66x_3_4_0_0/packages/ti/dsplib/src/DSPF_dp_lud/DSPF_dp_lud.h", line 43: fatal error #1965: cannot open source file "ti/dsplib/src/DSPF_dp_lud/c66/DSPF_dp_lud.h"
1 catastrophic error detected in the compilation of "../main.c".
The compiler is correct that file "ti/dsplib/src/DSPF_dp_lud/c66/DSPF_dp_lud.h" does not exist, but file "ti/dsplib/src/DSPF_dp_lud/C66/DSPF_dp_lud.h" does exist (changed /c66/ to /C66/ ).
I wonder if dsplib_c66x_3_4_0_0 for Linux host has some incorrect internal path names? There are seven internal subdirectories named "C66" (upper case) which possibly should be named "c66" (lower case) similar to the other 111 subdirectories that are named "c66". For example "dsplib_c66x_3_4_0_0/packages/ti/dsplib/src/DSPF_dp_lud/C66". Dsplib also has a couple of .h files containing windows style path separators "\" in include statements instead of unix style "/". They prevent compilation even after the directory paths are changed. With all these changes, the program compiles OK.
If I use the previous version of dsplib_c66x (dsplib_c66x_3_2_0_1) there are no c66 vs C66 path name problems, but there are some windows path separators that stop compilation eg dsplib_c66x_3_2_0_1/packages/ti/dsplib/src/DSPF_sp_erand/c66/DSPF_sp_erand.h says: #include "..\..\DSP_urand32\c66\DSP_urand32.h"
Am I misunderstanding how to use dsplib?
regards
-Keith