Hi,we are migrating our system from dspbios 5.x to sysbios6.I converted .tcf file to .cfg file successfully.I am using bios version 6.32.05.54code composer studio version is bios5.41.11.38 and the xdc tools version is xdctools3.22.04.46I am getting the following error while trying to buildthe workspace
1.could not open source file "xdc/std.h" at two different places 2. package/cfg/BiosSetup_p64Pcfg.cmd
Please help .
Aparna
Can you go to Project Properties->CCS Build->XDCtools->Advanced Options, and turn on -v option? Then please post the whole console log output.
If my reply answers your question please mark the thread as answered.
Hi Sasha:
The -v option was already on. The whole console log out is attached with this post.
Thanks
0447.log_out.txt
It seems that you have multiple projects referencing each other. The rule in Debug/subdir_rules.mk that should create configPkg/compiler.opt is overridden with the content of the same rule in other projects you are referencing, and that file is not created. All other errors are consequences of that file missing.
I don't know why CCS picks up makefiles from other projects, but you can try to work around it. How are your various projects related? Can you try cleaning BiosSetup project and then build your Lmuvob project?
HI Sasha :
BiosSetup is a folder that contains the *.cfg file ,*cfg.h and the platform folder. As suggested by you i have tried cleaning the project and rebuilding it. I have a peculiar problem now. Normally, the xdc/std.h error seems to occur even after explicitely including the xdc folder path . However, if i either add ( or exclude) some repositories under the RTSC tab of Build Options , I get SYS/bios 6 specific errors even though i am not using any Sys/bios 6 modules or APIs.
I am attaching with this post the list of the errors and the build log.
1513.error_1.txt
2112.b1_no_std.rtf
After you converted your config script, even though you are not calling SYS/BIOS 6 API directly, you are using SYS/BIOS 6 and any C error will refer to SYS/BIOS 6 modules.
These error messages#137 struct "ti_sysbios_heaps_HeapBuf_Struct" has no field "size" bioslapi.c /Lmuvob_14_1_SysBios line 2812 C/C++ Problem#137 struct "ti_sysbios_heaps_HeapBuf_Struct" has no field "size" bioslapi.c /Lmuvob_14_1_SysBios line 2814 C/C++ Problem#137 struct "ti_sysbios_heaps_HeapBuf_Struct" has no field "size" bioslapi.c /Lmuvob_14_1_SysBios line 2835 C/C++ Problem#137 struct "ti_sysbios_heaps_HeapBuf_Struct" has no field "size" bioslapi.c /Lmuvob_14_1_SysBios line 2837 C/C++ Problem#137 struct "ti_sysbios_knl_Semaphore_Struct" has no field "pendQ" bioslapi.c /Lmuvob_14_1_SysBios line 2388 C/C++ Problem#137 struct "ti_sysbios_knl_Task_Struct" has no field "environ" LMUMain.c /Lmuvob_14_1_SysBios line 608 C/C++ Problem#137 struct "ti_sysbios_knl_Task_Struct" has no field "environ" LMUMain.c /Lmuvob_14_1_SysBios line 617 C/C++ Problem#137 struct "ti_sysbios_knl_Task_Struct" has no field "name" bioslapi.c /Lmuvob_14_1_SysBios line 3063 C/C++ Problem#137 struct "ti_sysbios_knl_Task_Struct" has no field "stack" LMUMain.c /Lmuvob_14_1_SysBios line 526 C/C++ Problem#137 struct "ti_sysbios_knl_Task_Struct" has no field "stacksize" LMUMain.c /Lmuvob_14_1_SysBios line 527 C/C++ Problemwould happen if you accessed properties of BIOS objects directly. BIOS objects are meant to be opaque, and you should be using functions that access these objects. If you are only invoking functions, but still getting these errors, please post the code from your files that causes these errors.
The following errors are all referencing the same local symbol:#20 identifier "sL2Blk1" is undefined bioslapi.c /Lmuvob_14_1_SysBios line 2764 C/C++ Problem#20 identifier "sL2Blk1" is undefined bioslapi.c /Lmuvob_14_1_SysBios line 2924 C/C++ Problem#20 identifier "sL2Blk2" is undefined bioslapi.c /Lmuvob_14_1_SysBios line 2766 C/C++ Problem#20 identifier "sL2Blk2" is undefined bioslapi.c /Lmuvob_14_1_SysBios line 2926 C/C++ ProblemWhere is that symbol supposed to be defined? Is that a global referencing a BIOS object?
Hi:
After making certain code changes the previous errror messages have gone . Thanks. I now have linker error messages.
How to interpret error messages that go something like this - unresolved symbol - first referenced in bioslapi.obj. Attached with the post is the build and error log
thanks
8080.b_20_03.txt
7266.err_20_03.txt
Hi Sasha :
Thanks for your timely inputs . With a little help i can compile my application in sysbios.