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.

PC-Lint / Workspace format structure? / LintProject Professional



I'm researching a requirement to provide support for the .wks and .pjt file formats in our static code PC-Lint analyser application LintProject Professional - http://www.riverblade.co.uk/products/lintproject/index.html.

The Project .pjt file is a straight forward text file. format to process. The .wks format appears to be a serialised/binary file, is there any documentation available that someone here could link me to?

 

Thanks

- Beth Mackenzie

  • Beth,

    Workspaces (wks) are binary files that contain the serialized windows and data that were open when you saved the workspace in CCS.  They do also contain references to which projects are open in CCS which is probably the info you are trying to extract.  There is no documentation available on the workspace format and due to its nature it changes from version to version.

    The upcoming CCSv4 is Eclipse based.  This means that pjt files are replaced with Eclipse projects and workspaces change as well.  It is likely worth focusing your integration effort on the new release.  You can get the beta here:http://tiexpressdsp.com/wiki/index.php?title=Category:Code_Composer_Studio_v4

    Regards,

    John

     

  • Hi John,

    Thanks for your explanation on that matter. Since LintProject Professional is a command line application which auto generates project lint on for a selected configurations (for example in overnight build scenarios). Implementing the .pjt format with our existing implementation is reasonably straightforward. However as you say locating the correct data in a serialised data file can be difficult unless you have the right objects to go with it. Thank goodness for XML files! 

    Anyway, Visual Lint with Eclipse (is something we are already contemplating) is a different matter and will be an integration much like the Visual Studio integration that we support, and have a number of potential beta testers when we are ready on that one. 

    Beth