• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 2371 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Subclipse plugin incompatible with linked project files

E2E_display_name_Mike
Expert 1700 points

We use SVN for managing source code changes and are now in the process of integrating this into CCSv5.1.  We can download the subclipse plugin and notice it doesn't seem to work with linked files.  Our CCS projects contain mostly linked files (e.g. files residing outside the project folder).  This files aren't recognized by the plugin. The screenshot below illustrates the problem.  Files that are in the project folder show SVN info and can be compared to base versions in the repository.  files linked into the project won't do this.  Is this a bug?  Is there a workaround?  Thanks - Mike

  • 0
    TI__Guru*** 130875 points

    Hello,

    I am wondering if this might be, because in CCS there are two places you can enter include paths, build variables etc.   CCS when it builds, uses the CCS options as shown in this wiki.  I suspect subeclipse is likely using the generic eclipse ones.

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

    Could you please try the following and keep us informed.

    Try adding your paths and variables in the generic eclipse version of these options.  Many of these will be found under Project->Properties but you will need to show the advanced settings and go to C/C++ build.  Do you know if linked resources have the same problem in a generic eclipse project, non CCS?

    Best Regards,

    LIsa

  • 0 in reply to Lisa TI
    Expert 1700 points

    Lisa,

    I think my paths are already setup using the generic.  Can you look at the screenshot and tell?  Or give me an example of how I set this up?

    thanks - Mike

  • 0 in reply to E2E_display_name_Mike
    TI__Guru*** 130875 points

    Hi MIke,

    have a look at these two posting I found on google.  It seems this is normal subeclipse behaviour, however there are a couple work arounds it appears including svn:externals

    http://svn.haxx.se/subusers/archive-2006-05/0014.shtml

    http://svn.haxx.se/subdev/archive-2005-06/0119.shtml

    Please keep me informed whether this helps.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Expert 1700 points

    Hi Lisa,

    I looked into these posts.  Couple things. 

    1. It seems like this issue is common in any eclipse project containing linked resources, not just CCS eclipse.
    2. The solution is really to restructure your whole project so there is no linked resources.  In the repository, you can keep all your source files in whatever folder structure you like.  Then when you do a check-out, you direct SVN to take the files that are in a project and throw them all into one working folder that will be the eclipse project folder.  Then there are no linked resources;  everything to build your project is in one folder.  When changes are made and committed back to the repository, they are made back in the original repository location.  So it kind of flattens the folder structure into one.  We don't prefer this solution as it means we need to basically create a project from scratch and do some research how to script all this (for every eclipse project!).  It also means our working copy isn't a "mirror image" of the repository anymore.  This now becomes a bigger decision on if we want to change the way we structure/manage our dev projects.

    I think for now we'll just do all our SVN management outside Eclipse (as we were doing before upgrading to CCS5.1) and perhaps transition to what subclipse suggests at a later date.

    thanks,

    Mike

  • 0 in reply to E2E_display_name_Mike
    TI__Guru*** 130875 points

    Hi Mike,

    ok, thanks for the update and feedback.  All the best with development.

    Best Regards,
    Lisa