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.
Hello,
I created a dynamic executable and i wanted to test it with a simple dynamic library. I follow the tuto that is describe in : . But i have a problem. When I want to build my dynamic library, i have : fatal error : could not open source file "stdio.h". I tried to add it in the current directory, and it did not work. I tried to add the path (with the cl6x compiler, option -i) to the library (which is in the include directory in CCS) and it did work even. I created a ccflag.cfg within there is only this : -i"D:\APP\TI\CCStudio_v5.5.0x86\ccsv5\tools\compiler\msp430_4.2.1\include". But it did not work. The only thing which worked is when i wrote : #include <D:\APP\TI\CCStudio_v5.5.0x86\ccsv5\tools\compiler\msp430_4.2.1\include\stdio.h>. But it did not find anothe header file; that mean i have to change all the files in the include directiry. It is too dangerous and it is not a clean method.
Can you help me please
PS : I put : cl6x -mv6740 -abi=eabi hello.c -z --dynamic=lib cmd_file=ccflag.cfg -o hello.elf oe.exe -entry_point=start into the windows terminal. I work on EVMC6748 DSP connect with a XDS510 USB on CCS v5_5
If you need more informations let me know. and sorry for my english.
Your trouble with accessing stdio.h has nothing to do with dynamic linking, so I will ignore that part of things for now.
The problem with this ...
Alexandre Aubry said:-i"D:\APP\TI\CCStudio_v5.5.0x86\ccsv5\tools\compiler\msp430_4.2.1\include"
... is that it refers to the MSP430 compiler include directory, not the one for the C6000 compiler.
And I'm still not sure exactly how you carry out the build. Do you build from within CCS, or from the command line? For now, I presume you build from within CCS.
I need to see everything that happens during a build. Please post the entire contents of the Console view from a build. Use the icon in the upper right bar of the Console view titled Copy Build Log. Give the file the extension .txt. Attach it to your next post. When you post, click on Reply, then Use Rich Formatting. The message compose interface includes an icon that looks like a paper clip. Use that to attach the file.
Thanks and regards,
-George
I did it with the Windows command line and not with CCS, i did not find how to do with CCS to build my dynamic executable and and my dynamic library.
I changed the path into the ccflag.cfg in order to go into the include of the C6000 copiler but it does not change anything.
This the error into the Windows command line :