• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 53 subscribers
  • Views 741 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.

One file across two projects (CCS 5.4)

Wil P.
Expert 1650 points

Hello,

I am developing on the Concerto processor and want to share a few H files between the two projects (one for each core).  Is there any way that I can have one file that will be included in both builds?  Right now, when I update the file, I have to copy it to the other project.

Ideally, I would like this to not be attached to either of the projects, if that is possible.  Like, for example, if I could store it in the workspace itself.

Thank you,

Will

  • 0
    TI__Guru*** 130875 points

    Hi WIlliam,

    If these two projects are yours alone and on the same pc ... I would recommend perhaps linking in the header file ... created it as a linked resource in both project.  If you are sharing this across drives/people ... most people use revision control however see the below wikis.

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

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

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

    Please keep us informed whether this helps.

    Best REgards,
    LIsa

  • 0 in reply to Lisa TI
    Expert 1650 points

    Hmm, Thanks to your suggestion, I think I have found a solution but I would like an opinion on it.

    My current development environment is a small team where we manually export and upload our projects into a central repository. At most, there is one person working on the project at a time, but eventually it will shift between users.  it needs to be portable using the Export function.

    I think a solution for me would be to make a third project called "Shared files". The shared files will exist there and then I will use relative links in each of the actual working projects.

    I do not like the idea of a third project, but I want to be able to export a single archive file at a time whilst also not having the file attached to either project.

    What do you folks think, is there a better solution for my needs?

    I would gladly accept help from end users and TI employees alike. Thanks.

  • 0 in reply to Wil P.
    TI__Guru*** 130875 points

    Hi William,

    I have been putting this by some colleagues as well.   The export should work however is something we only recommend with caution.

    Aside from this you probably have found one of the best "work arounds"

    Hope this helps.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1650 points

    Lisa,

    Can  you provide some detail on the "caution"?  I know exporting/importing is not ideal but why caution?

  • 0 in reply to Wil P.
    TI__Guru*** 130875 points

    Hi William,

    well, it is mostly because it is not known to be completely bug free and actually was a bit better in v4, however that does not mean not to use it.   It is simply not the typical ... but again in your case I would certainly say to proceed.

    Best Regards,
    Lisa

  • 0 in reply to Wil P.
    TI__Guru**** 464751 points

    William,

    The reason we advise against using the export to archive feature is because of a known Eclipse bug that was introduce in Eclipse 3.6 and greater (CCSv5 is based on Eclipse 3.6+):

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=355049

    In short, the linked resource information in the original project is not properly preserved. This breaks the ability of the import archive feature to properly reconstruct the linked resource file directory structure (it instead copies the file into the project folder). Since your idea involves linking the header file from the 3rd project, it will cause issues.

    I would abandon the export to archive functionality and instead look at adding the files to source control not in an exported archive

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1650 points

    Ki-Soo,

    Thank you very much for your information!

    Is there a "Source Control for Eclipse for Dummies" guide somewhere?

    What we are doing here is a joke, I admit, but no one here has the expertise to fix it.  

    Teach a man to fish, nah'mean?

  • 0 in reply to Wil P.
    TI__Guru**** 464751 points

    The way most people work with source control is they make the their project "portable" and then check in all their source repository and project metadata files.

    How to make a project portable: http://processors.wiki.ti.com/index.php/CCS_Modules_Library#Portable_Projects

    Note the above is a lab but you don't have to actually do the lab to learn the concepts.

    What project metadata files to check into source control:

    http://processors.wiki.ti.com/index.php/FAQ_-_CCSv5#Q:_Which_project_files_do_I_need_to_check_into_source_control.3F

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 173310 points

    Just to add to Ki's response, an additional wiki article on using source control with CCS that may be helpful: http://processors.wiki.ti.com/index.php/Source_control_with_CCS