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.

CCSV5 can't build rts430xl.lib

We've been using the 90 day free license on an internet capable PC up until now.  We just installed a 3 seat floating license verion of CCSV5 on a stand alone, internal network.  I moved my workspace over, and attempted to compile my project.  It is a large memory model, and the link fails because the CCS attempts to build the rts430xl.lib for first time use.

The make fails with the error:   "Multiple target patterns".  We are using the 5438A version.

Does anyone know what this is, and what will fix it?  I have admin rights on that PC, so it shouldn't be a permissions thing.  I assume the error that's getting printed probably isn't representative of what the real problem is.

Thanks,

Joe B.

  • Hello team,

    Is there an update available regarding this customer inquiry?

  • Hi Joe and Michael,

    I'm going to move this thread to the CCS forum, I think you will get better support on this particular issue there.

    In addition, can you please copy the entire contents of your build console into a text file and attach it? This will help our CCS team debug this by providing more specific information about the build and exactly what errors are occurring.

    Regards,

    Katie

  • Joe,

    I was able to build the same library in my setup here, therefore the issue may be caused by something else.

    When you say you moved your workspace, how exactly did you do this? The reason is that Eclipse workspaces have lots of information tied to their physical location in the system and therefore it is possible the contained projects may have become corrupt.

    The error you mentioned may be related to that, but to get additional insight about it the information suggested by Katie will be needed.

    Regards,

    Rafael

  • I copied the entire workspace and placed it on the C drive.  The only difference is the PC that it is on (i.e., C:\CCS_Workspace on both PCs).  As an experiment, I decided to move that same workspace to another PC (this one acutally) where I do not have admin priveledges, so I had to locate it deep in the bowels of the MS dir structure (C:\Documents and Settings\blodgjo\CCS_Workspace) where I am allowed to store things, downloaded a free copy of CCS and installed that where our IT guys will allow (C:\temp\Ti), and built my project (and library) w/o an issue!?  I copied the library I built here over to my PC where I can't build the library, and at least I can now compile and test now....I just don't have 100% confidence that that library is identical to the one that would be built on the other machine...if it could build one....and that I am going to run into trouble later on down the road.

  • Hmmm, interesting. Is the library project dependent on the main project? If so, it is possible you are hitting the Eclipse bug shown here - although it does not seem to exactly explain why the project is properly built in the other workspace.

    Another alternative is to check a different scenario that I had seen before: even with full admin privileges, I sometimes hit a problem where some directories do not enable write privileges when I create them. In this case I explicitly enable Full Control for regular users similarly to what is shown at this post - can you try that in your C:\CCS_Workspace and see if it works?

    I will get back to this post if I have additional ideas.

    Hope this helps,

    Rafael