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.

compiler definition not available

Other Parts Discussed in Thread: OMAP3530

Hi

 

I've updated to the latest CCS, v5.2.0.00069, and now I cannot open my old project anymore. I get an error, saying "... compiler definition not available..." and CCS refuses to open the project.

Note, if I open the project with my older 5.1.0.09 CCS, it works fine. Also, if my workspace contain the old ".metadata" folder from 5.1.0.09, I can open it with v5.2.0.00069

BR

N

  • Niklas,

    Your query does not seem to be BIOS related, so I moved this thread to the CCS forum in hopes that it will get a faster response there...

    Dave

  • Hi Niklas,

    please try updating again and see if you find the update to build 70.  This should resolve your issue.  Keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa

    I used CCS menu option "help->check for updates", but I couldn't see build 70 there. Do I need to do something special?

    BR

    Niklas

  • HI Niklas,

    ok I think you will either need to install fresh or I can send you a link offline with a fix.  Do you have a preference?

    Best Regards,

    Lisa

  • hi lisa

    please send me a link.

     

    br

    niklas

  • Hi Niklas,

    ok, I got your message.  The only thing left that I can suggest is to install fresh.  You can download CCS here:

    http://processors.wiki.ti.com/index.php/Download_CCS

    Best Regards,
    Lisa

  • Hi

     

    The latest version on that page is the 69 build, not the 70 build ?

    where do I find the 70 build?

    BR

    Niklas

  • HI Niklas,

    installing fresh means you won't need 70 ... so please give it a try.  If you still have issues, just let us know. 


    Best Regards,
    Lisa

  • Hi Lisa

     

    Now I don't understand at all. What I did in the first place was to make a clean installation of the 69 build, which gave me the issue I reported. Why would re-installation of the 69 build fix the issue, when you fixed something in the 70 build?

    BR

    Niklas

  • Hi Niklas,

    the problem is caused by the updating ... this is why a fresh installation should get your issue resolved.  Sorry that this may not have been clear.


    Best Regards,
    Lisa

  • Hi again

    unfortunately, it's still not clear. I did a clean installation of the 69 build in the first place, no web update. So this this is why I'm confused. Why would a second installation of the exactly the same build fix anything?

     

    BR

    N

  • HI Niklas,

    ok I appologize, I think I misinterpreted when you said "Updated to v5.2". 

    Have you tried importing the project?  What do you mean by "open the project"?  Have you tried a fresh workspace?

    Best Regards,
    Lisa

  • Hi Lisa

     

    yes, i tried project->import existing ... And this is what fails. It is when I use a fresh workspace it fails. if I use an old workspace, previously created by my 5.1.0.09 ccs, it works.

     

    br

    niklas

  • Hi Niklas,

    can I just confirm you use the import CCS project?  Project->Import existing CCS/Eclipse Project?  Do all your projects/workspaces show this behaviour?  Do you have a small test case you could send us to try and reproduce this?    What target are you using?  What compiler?  Could you please send a few more details?

    Best REgards,

    Lisa

  • yes i use Project->Import existing CCS/Eclipse Project. yes, all of my projects shows this behaviour. No test case, but I'm attaching my .project file below.I have four targets, omap3530,omap4430,ti814x and c674x simulator. cgtools 7.3.5

    br

    Niklas

    .project-file below

    <?xml version="1.0" encoding="UTF-8"?>
    <projectDescription>
     <name>RMC_PLUS</name>
     <comment></comment>
     <projects>
      <project>10025469_A8DSP_SharedHeader</project>
      <project>10025469_SharedHeader</project>
     </projects>
     <buildSpec>
      <buildCommand>
       <name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name>
       <triggers>clean,full,incremental,</triggers>
       <arguments>
        <dictionary>
         <key>?name?</key>
         <value></value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.append_environment</key>
         <value>true</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.autoBuildTarget</key>
         <value>all</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.buildArguments</key>
         <value></value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.buildCommand</key>
         <value>make</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.buildLocation</key>
         <value>${workspace_loc:/RMC_PLUS/build/j5/debug}</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.cleanBuildTarget</key>
         <value>clean</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.contents</key>
         <value>org.eclipse.cdt.make.core.activeConfigSettings</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.enableAutoBuild</key>
         <value>false</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.enableCleanBuild</key>
         <value>true</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.enableFullBuild</key>
         <value>true</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.fullBuildTarget</key>
         <value>all</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.stopOnError</key>
         <value>true</value>
        </dictionary>
        <dictionary>
         <key>org.eclipse.cdt.make.core.useDefaultBuildCmd</key>
         <value>true</value>
        </dictionary>
       </arguments>
      </buildCommand>
      <buildCommand>
       <name>org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder</name>
       <triggers>full,incremental,</triggers>
       <arguments>
       </arguments>
      </buildCommand>
     </buildSpec>
     <natures>
      <nature>org.eclipse.cdt.core.cnature</nature>
      <nature>org.eclipse.cdt.core.ccnature</nature>
      <nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature>
      <nature>org.eclipse.cdt.managedbuilder.core.ScannerConfigNature</nature>
     </natures>
     <filteredResources>
      <filter>
       <id>1324540500913</id>
       <name></name>
       <type>26</type>
       <matcher>
        <id>org.eclipse.ui.ide.multiFilter</id>
        <arguments>1.0-name-matches-true-false-CMakeFiles</arguments>
       </matcher>
      </filter>
      <filter>
       <id>1324540500975</id>
       <name></name>
       <type>30</type>
       <matcher>
        <id>org.eclipse.ui.ide.multiFilter</id>
        <arguments>1.0-name-matches-true-true-_DRA446|_OMAP3530|_FRANKENSTEIN|_SIMC67|_TI814x</arguments>
       </matcher>
      </filter>
     </filteredResources>
    </projectDescription>

  • Hi Nicklas,

    Could you please send us your .cproject file from the root of your project?  And also your <workspace>/.metadata/.log file.

    Thanks,

    - Baltasar

  • Hi Nicklas,

    Your project is not a "CCS Project".  Please try importing it using the File > Import... > General > Existing Projects into Workspace wizard.  

    For CCSv5.2.1, I've added logic to detect this case, and instruct the user on how to import non-CCS projects.

    Thanks,

    - Baltasar