• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 856 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Question about importing AM572xx makefile based projects in CCSv6

Daniel Castagnola Weckesser
Intellectual 410 points

Hello,

After importing a makefile based project (by creating a new "Makefile project with existing Code") it's usually necessary to pass the project a lot of variables that feed the makefile to work right. In the AM57xx pdk there's a batch file (pdksetupenv.bat) that creates these variables for command line building.

Instead of manually write them one by one in each project, is it possible to automaitcally import them all from a predetermined file?

(I am currently using a tricky approach consisting in executing the CCS from a batch file that previously called pdksetupenv.bat, but I hate it almost as much as retyping all that stuff).

Thank you very much,

Daniel

  • 0
    TI__Guru**** 170244 points
    Daniel,

    I am not 100% sure how the projects you are using were created, but I suspect there is no easy way to add these variables "in bulk" if you are using pure makefile projects. The reason being these types of projects rely on the IDE settings only for very minor settings and leave the project settings to the makefile itself.

    That said, there are a few methods that allow a managed project inside Eclipse to make use of such variables.

    CCS projects have a file named macros.ini that allows adding build and path variables automatically when importing a project to the workspace - something described at section 4.1.3 of the page below:

    processors.wiki.ti.com/.../Portable_Projects

    This mechanism works for CCS projects only, but there is a way to simply import a macros.ini project to your workspace and set the variables. In this case the variables may be used by both CCS projects and Eclipse's C/C++ projects.

    Please give these suggestions a try and see if you can accomplish what you need.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Intellectual 410 points

    Rafael,

    Thank you for your reply. As you suggested importing a "macros.ini" or similar file to the entire workspace does work right. If  sharing them among all the workspace is a problem for some workspace's projects another option is to write these variables in a secondary makefile to be included only in the main makefile of the projects of intererest.

    Thanks,

    Daniel

  • 0 in reply to Daniel Castagnola Weckesser
    Intellectual 410 points

    Hello Rafael,

    I have to retract from my last post. Variables introduced via importing macros.ini end up defined in "Project Properties -> Resources -> Linked Resources -> Path Variables" wherefrom they have no visibility to the makefile. It seemed to work just because those variables stayed declared from a previous session in "Project Properties -> C/C++ Variables -> Environment" , and I didn't realize that until now. So, is there any way to import a bunch of variables to there in CCS v6.1.3 ?. As I told you I am currently defining them within a secondary makefile to be included in the first line of the main makefiles.

    Thanks,

    Daniel