• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 1051 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.

is there a way to copy in one folder all the dependencies and files of a project?

apfausto
Prodigy 245 points

Hi all,

I'm working on a Bluetooth firmware example. This project uses libraries and files that are not in the project folder . Since I have to work with a team and we are going to use GitHub; is there a way to put all the project files in a single folder so that I can share easily the code?

Fausto

  • 0
    TI__Guru**** 173310 points

    If you are looking for tips on creating portable projects (that can be easily shared among multiple users), please see this wiki:

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


    If, on the other hand, you are looking for a way to identify all the files that are part of an existing project so you can copy all of them into a single location, then there a few steps to take (there is no simply, single-click button button to do it):

    For Source files:
    Copied resources (resources that reside in the project folder) are easy to identify.  For linked resources, the .project file would list all linked source files.
    Another way to get the list of files (both copied and linked) would be to export the project (menu File->Export->Archive File) and it will pull all the referenced files into the archive even if they are linked.

    For Header files:
    If they are either copied or linked to project, then the above methods would work. However if they are only referenced in #include statements and "found" using compiler search path then that method wouldn’t work. In that case, you can build the project with the compiler option “Generate include file dependency information” and this will generate a file with the list of header files. To enable this option, the Parser Preprocessing mode (under Build->Compiler->Advanced Options->Parser Preprocessing Options) should be set to manual rather than automatic.

    For Library files:
    Similar to Header files, if they are either copied or linked to project, then the export method would work. If they are only referenced in the linker --library option, you can check the .cproject file to see which libraries are specified under the --library option.

    Hope this helps!

  • 0 in reply to AartiG
    Prodigy 245 points
    I really appreciate your help!

    I read the guide to export the complete project (Portable Projects); but I still have one problem: when I import the project in the workspace it will use the same paths before exporting, even if there are all the files needed in the project folder. Should I change manually all the path?
  • 0 in reply to apfausto
    TI__Guru**** 173310 points

    fausto Annicchiarico Petruzzelli said:
    when I import the project in the workspace it will use the same paths before exporting,

    That is how the export/import feature is designed to work. If there are linked resources in the project, then it will preserve its paths during export and extract them to the same paths after import. 

    If all the files required for a project are within the project folder itself, then it is sufficient to simply zip up the project folder and share it with others.