Hello,
trying to compile FFTW for C6747 (I need FFTs far bigger than 8k lines of DSPLIB), I ran into some trouble. After I managed to compile and ar all C files, compilation is succeeding, but the linker complains:
'Invoking: Linker'
"C:/Programme/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 7.2.2/bin/cl6x" -mv6740 -g --diag_warning=225 -z -m"fftw_benchmark.map" --warn_sections -i"C:/Programme/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 7.2.2/lib" -i"C:/Programme/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 7.2.2/include" -i"C:/Programme/Texas Instruments/bios_5_41_10_36/packages/ti/rtdx/lib/c6000" -i"C:/Programme/Texas Instruments/bios_5_41_10_36/packages/ti/bios/lib" --reread_libs --rom_model -o "fftw_benchmark.out" -l"./fftwf_benchmarkcfg.cmd" "./main.obj" "./fftwf_benchmarkcfg_c.obj" "./fftwf_benchmarkcfg.obj" -l"D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib" -l"libc.a"
<Linking>
undefined first referenced
symbol in file
--------- ----------------
_fftw_dft_conf_standard D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<configure.obj>
_fftw_mkplan D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<plan.obj>
_fftw_mkproblem D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<problem2.obj>
_fftw_mkproblem_unsolvable D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<problem2.obj>
_fftw_plan_awake D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<apiplan.obj>
_fftw_plan_destroy_internal D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<apiplan.obj>
_fftw_problem_destroy D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<apiplan.obj>
_fftw_rdft_conf_standard D:\Projekte\ccs\fftw-3.2.2\lib\fftwf.lib<configure.obj>
error: unresolved symbols remain
While compiling fftw with cl6x -c -mv6740 --gcc -fr ./lib --verbose I got this message:
TMS320C6x C/C++ Compiler v7.2.2
Tools Copyright (c) 1996-2011 Texas Instruments Incorporated
"dft/conf.c" ==> fftw_dft_conf_standard
ar6x rv fftwf.lib *.obj said:
==> add 'conf.obj'
So _fftw_dft_conf_standard should be well defined and available for the linker. I have tried to add conf.obj manually to the linker search path or to copy it directly to the project, nothing helped.
Any ideas?
TIA,
Markus