> Cannot Open
> Cannot Open Source File Xdc/std.h
Cannot Open Source File Xdc/std.h
I still have the same error. Innovate TI Live @... Note it did NOT create a migration.log file. 10) Now see\Codecs\vidanalytics_copy 11) NOTICE STUPID ECLIPSE BEHAVIOR: new project has source code files from example, but it only linked to Paths for system variable or XDC Tools settings in CCS Build -> XDC Tools) When i tried to build - cannot find the file "./configPkg/Linker.cmd"... Source
Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Mastermind 6735 points Helmut Forren Jan 10, 2011 7:48 PM In reply to Helmut Forren: "EDIT" above fixed the xdc/std.h problem What build of CCS4.2 do you have? This problem is probably due to using incompatible versions of the cygwin DLL. I am including in my main.c file. https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/218574
A RTSC configuration project encapsulates all the information required to consume RTSC content like SYS/BIOS and IPC. They should be more familir with building it. Please have a look at the wiki I sent and use those include paths and options.
Can you verify this version does have a bug on the example on your end? 2. As a result, the 64-bit types described here may not be defined for all targets. Now lets analyze the symptoms of the problem that you are seeing. I find that the Include folders under the project panel tree indeed come from the build properties setting.
This should popup a text box with the script fragment required in your configuration script. Regards Amit ------------------------- Don't forgetto verify answersto your forum questions by using thegreen"Verify Answer" button. Use of the information on this site may require a license from a third party, or a license from TI. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these
XDCtools internally uses utilities distributed with cygwin. cl64P package/cfg/common_p64P.c ... Follow Us TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | m.ti.com (Mobile Version) TI is a global semiconductor design and manufacturing company. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at
Content on this site may contain or be subject to specific guidelines or limitations on use.
Look at the generated 'configPkg' folder in your RTSC configuration project for these files. http://rtsc.eclipse.org/docs-tip/Demo_of_RTSC_Project_Creation_in_CCSv4 P.S.: I did a Software Update and re-ran it, still the same. For example, the type Bool can also be written as "xdc_Bool". Check This Out Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Prodigy 135 points steven149 Apr 28, 2010 4:58 PM In reply to AmitMookerjee: Amit, Thanks for your reply.
Good point. If you haven't read it in awhile, please read it again to see if any updates were made. not all compilers provide C99 type support; if XDC supplies the type definition and the compiler is updated to include C99 types, a compilation error will occur if the source includes Where appropriate, the types defined below are related to the types defined in the library headers prescribed by the C99 standard (ISO/IEC 9899:1999).
Use of the information on this site may require a license from a third party, or a license from TI. Bug320943 - Can't use a Module API name as a project name if xdc/cfg/globals.h is included Summary: Can't use a Module API name as a project name if xdc/cfg/globals.h is included This type is defined if and only if the preprocessor macro xdc__INT64__ is defined. Long names exist to avoid conflicts with names defined or used by existing code bases.
Bits64 unsigned integer type that is precisely 64 bits wide. Use of the information on this site may require a license from a third party, or a license from TI. http://rtsc.eclipse.org/docs-tip/Demo_of_RTSC_Project_Creation_in_CCSv4 It seems the interface somehow changed a bit compared to the tutorial.