• Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 1024 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.

Parsing compiler output using external makefile?

Jordon
Intellectual 635 points


Hello,

I have my project calling an "external" makefile but the processing of the make output in the build window does not seem work like it does when building from normal projects. When an error/warning is output in the build window, usually you can click it to open up the file to the warning\error. This does not seem to work for me however he hide error/warning filters seem to work but the "find next warning/error" functions do not...

Hopefully this is something easy...

Thanks. Jordon

  • Prodigy 40 points

    I have also run into this problem.   I exported a project file to an external makefile, and errors and warnings do not seem to be parsed, so that I can click on the message and jump to the warning/error in the file.  Does anyone know how to fix this?

  • TI__Genius 15710 points

    Jordon, 

    Are you using CCS v4.x? Could you check which error parsers are enabled in your project? (right click on project; select properties; click on C/C++ Make Project and then choose Error Parsers tab. 

     

     

    Martin

     

  • in reply to MartinS
    Prodigy 40 points

    No, I'm using version 3.1

  • in reply to MartinS
    TI__Genius 15710 points

    Dan, 

    Sounds like you are using CCS v3.3? Could you provide more details on how you have setup build of a makefile within CCS 3.3?

     

    martin

     

  • in reply to MartinS
    Prodigy 40 points

    I exported the makefile from an existing project, and then created a new project, using the menu item Project -> Use External Makefile, that calls the external makefile.  The corresponding config file sections appear as follows:

    [External Makefile]
    ExtMakefile=Makefile

    ["Makefile" Settings: "Debug"]
    UseCustomBuild=true
    CustomBuildCmd=..\..\make_all.bat
    CustomBuildOutput=".\build\debug\debug_build.out"
    CustomCleanCmd=..\..\clean_all.bat

    The make_all.bat and clean_all.bat set up the build environment variables by calling the DosRun.bat file provided with code composer.  They then call the makefile using emake or clearmake depending on whether the build happens locally or on an electric cloud server.

    the builds work correctly and the build progress shows in the build window, but when I go to click on an error or warning item, it is not hyperlinked to the corresponding source file.

     

     

     

     

  • in reply to Dan Wickstrom
    TI__Genius 15710 points

    It appears to be a bug. Unfortunately, we do not have any service releases planned for CCS v3.x products. However, it seems somewhat roundabout to create a ccs project, then generate a makefile from it and then reimport generated makefile. If the goal is to have the same "source" project be used on an automated build machine and within CCS, then could timake be used? timake is a command line tool that builds .pjt files. I am not 100 % sure, but I think it is available in CCS v3.1 (CCSInstallRoot\cc\bin)

     

    martin

     

  • in reply to MartinS
    Prodigy 40 points

    It seems roundabout, but it's not.  We have existing projects that were bult using either clearmake callling timake or from within ccs.  We now have electric cloud servers to speed up builds, but timake is not usable, since electric cloud doesn't understand how to parse .pjt files, so there isn't any possiblity to build in parallel on electric cloud using timake.  Exporting the .pjt files to makefiles allows electric clould to buld the objects in parallel (build times reduced 8x), but I would like to retain the possiblity to build within ccs for the developers that prefer ccs as a development tool.  Not having the the hyperlinking is small inconvenience, but it will be irritating for the developers that like to use ccs.