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.

Linked resources in an imported project

Hi,

I'm trying to import multiple legacy 3.3 projects into CCSv5 workspace, but I'm facing some problem resolving the path variables and linked resources. Can somebody elabaorate the differences between the following linked reosurces:

What is the difference between Parent_Loc and Workspace_Loc, SRC_ROOT and COMMON_ROOT?

I have 3 folders containing my 3.3 project:

projectfiles: This contains the .mak,.pjt files, etc. of the projects.

project: This folder contains the .ccsproject,.cdtbuild, macros.ini files and the .metadata folder of the project files.

Source: This contains the source files.

I have created a new folder in the same location and trying to import the projectfiles into the new folder, but then unresolved paths appear. What COMMON_ROOT should be specified while importing the project?

  • Hi Jasmeet,

    have you used the import wizard?  Under Project->Properties->Import Legacy CCSv3 Project? 

    This might be a useful wiki topic for you and help you resolve any broken links.

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

    Regarding the differences in the path variables you specifice ... have a look at the wiki .. this will lead to to the settings where these are defined and you can see exactly for yourself. 

    I hope this helps.  Please keep us informed.

    Best Regards,
    Lisa

  • Lisa,

    I'm using the import wizard itself, and I also read the wiki page, but I'm still not very clear about the differences between Parent_Loc and Workspace_Loc, SRC_ROOT and COMMON_ROOT. Parent_Loc and Workspace_Loc essentially look similar to me.

    I resolved the errors though, by using the appropriate include options. Thanks.

  • Hi Jasmeet,

    these are all path variables used to make is easy for you to add linked resources with a relative path ... for example relative to the workspace location so you don't have to fill in the entire path every time.

    Although some of these are eclipse predefines (and there is useful information on the eclipse sites as well) you can of course add your own.

    http://help.eclipse.org/helios/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Fconcepts%2Fcpathvars.htm

    http://help.eclipse.org/helios/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2FresAdv_variables.htm

    I am not an authority on path variables but I believe for example

    workspace_loc - location of the current workspace

    parent_loc - location of the workspace the linked resource belongs to  (although once again this is simply a variable that substitutes a specific path)

    src_root and common_root ... I believe again src_root may be a directory specifier to a pool of code specific to the current project.  common_root may be a path specifying a common code repository somewhere.


    But once again what you define and how you use these is up to you and your code structure. 

    I am glad the errors got resolved and all the best with development.

    Best Regards,

    Lisa