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.

Compiler/PROCESSOR-SDK-C674X: dsplib 3.4.0.0 compilation error for DSPF_sp_blk_move

Part Number: PROCESSOR-SDK-C674X

Tool/software: TI C/C++ Compiler

Hello all,

I'm using dsplib 3.4.0.0 (latest one as for today) and get the following compilation error when calling the function DSPF_sp_blk_move:

#20 identifier "DSPF_sp_blk_move" is undefined   

I believe the problem is that the file DSPF_sp_blk_move.h contains a typo.

It should be

#ifndef _DSPF_SP_BLK_MOVE_H_
#define _DSPF_SP_BLK_MOVE_H_ 1

instead of

#ifndef DSPF_sp_BLK_MOVE_H_
#define DSPF_sp_BLK_MOVE_H_ 1

on the top of the file.

I think this issue has already been addressed in the following topic, though with a different version of the library and a warning instead of an error:

e2e.ti.com/.../292027

Best,

Edgar

  • Edgar,

    I believe the bigger issue is that there are 2 version of the header file in the library in the following locations.

    • dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move\DSPF_sp_blk_move.h
    • dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move\c674\DSPF_sp_blk_move.h


    And both the headers have that same MAcro (DSPF_sp_BLK_MOVE_H_) defined so when you include dsplib.h or DSPF_sp_blk_move.h from the folder dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move that macro gets defined and it includes the header from location dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move\c674\ but since the macro is already defined the header never gets to the function declaration.

    My recommendation would be to not use dsplib.h or DSPF_sp_blk_move.h (from location dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move\) but to directly use header file at location dsplib_c674x_3_4_0_0\packages\ti\dsplib\src\DSPF_sp_blk_move\c674\

    Let me know if this resolves the issue. We have filed a bug report for this and I will let you know when I have a timeline when this issue will be fixed.

    Regards,
    Rahul