• Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 992 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Tool to automatically convert CCS4 compilation to Command Line Version?

Thomas Price7137
Intellectual 625 points

Other Parts Discussed in Thread: OMAPL138

I am trying to compile my OMAPL138 project (ARM side) using just the command prompt. I have successfully built this project in CCS4 many times. I am also aware of the document SPNU151F which describes how to compile from the command prompt. However, I don't quite know how to convert the exact equivalent used in CCS4 into command prompt form. I've looked at the makefiles in the Debug folder but they are very complicated and convoluted. They point to a bunch of sub-makefiles, so it is difficult to follow what is going on. Is there maybe a tool that would convert the CCS4 compilation into something I could use to compile from the command prompt?

In case you are wondering, I need to compile from the command prompt because Klocworks requires that for static analysis of my code.

  • TI__Guru**** 253380 points

    Please see this wiki article.

    Thanks and regards,

    -George

  • in reply to George Mock
    Intellectual 625 points

    George-

    I've seen this article already and it appears to me that everything shown here is java based. Klocworks on the other hand will be filtering for the keyword "cl470" (the actual compiler command. So I'm not sure it will recognize the java only lines as belonging to any compiler it recognizes.

                         -Thomas

  • in reply to Thomas Price7137
    TI__Guru**** 163045 points

    Thomas,

    I believe there is a klocwork integration for CCSv4 already.  Have you tried it?

    John

  • in reply to JohnS
    Intellectual 625 points

    I have not tried it. Do you know where I can find more information about that?

  • in reply to Thomas Price7137
    TI__Guru**** 163045 points

    Thomas,

    It is available from Klocwork.  I have seen some demos and it looks very nice.  The klocwork analysis displays show up within the CCS environment.  It is tied into your builds within CCS.  Pretty nice integration.

    Regards,

    JOhn

     

  • in reply to JohnS
    Intellectual 625 points

    So I think what you are referring to is the tool that "users" can add as a plug-in to build and compare to the image on the "server". What I am trying to do is build the base image that is loaded on the build machine. This base image is then loaded onto the "server" machine. From there "users" can use the Klocworks Eclipse plug-in to verify their builds in CCS4. I will check with the Klocworks FAE though to see if this tool can also be used for the initial build to be uploaded on the server. From what I have been told though, that was not the case.

  • in reply to Thomas Price7137
    TI__Guru**** 163045 points

    We could be talking about different things.  What I am talking about is the desktop analysis software from klocworks.  It can do static source code analysis, has some build analysis tools, collaboration...  Their website talks about how it can tie into Eclipse build systems.

    If you end up needing to build CCS projects from the command line the wiki link George sent shows how to do this.  You are correct that it is java/javascript telling CCS what to do.  However the output is echoed to the dos shell and it looks just like it does from within CCS, same as what is shown in the console in ccs.  It shows the exact command sent to the compiler and the feedback from the compiler, so the klocworks tools should be able to parse it ok.

    John

  • in reply to JohnS
    Prodigy 10 points

    Thomas,

    If you can't figure out how to compile from the command line you can still try using Klocwork.

    1. Run kwinject in a command prompt before using CCS: kwinject <ccs.exe> (or whatever the executable is called)

    2. Run a build as normal in CCS

    3. Exit CCS

    4. Now in your current directory you should have a kwinject.out file so you can run a Klocwork build.

    alen