Automatically import referenced projects CCS5.3

HI David,

what exact warning/error do you get?   I just tried a simple case with 2 referenced projects and all three were imported without issue together into my new workspace.

Would you be able to send a test case/steps to see if we can reproduce the same behaviour here?

It would also help to know the exact ccs version you use and the ccs version the projects were created in.

Best Regards,
Lisa

Hi Lisa,

I am using CCS 5.3.0.00090. These projects were originally created in CCS 3.3, but have since been ported over to CCS5 projects.

Here are my steps:

Open Code Composer 5

Go to File->Import

Select "Existing CCS Eclipse Projects" under Code Composer Studio

Browse to the directory containing the projects

Select the "main" project, which references all of the other projects

Select "Automatically import referenced projects"

Click Finish.

The following screen shot is what I see

If I manually check each project they import successfully.  Is there an exmple project I can try to see if it works?

Thanks,

David

Hi David,

that error unfortunately does not say much and I can not reproduce this importing here.  The one thing I have not done is try to import a mixture of v3.3 and v5 projects.  This I would expect to fail as there are two different import paths for them.

Have you converted all projects to v4/5 projects first?  You will need to do this.  v3.3 projects are not eclipse based and need to be imported/converted using Project->import legacy ccsv3.3 projects first.

Best Regards,
Lisa

Lisa,

The projects should all be v5 projects.  If I use the same mechanism to import them but select them manually they import ok using the "Existing CCS Eclipse Projects" option.

David

Hi David,

ok I think the next steps would be the following

- double check all are v4/5 projects

- how are you creating the dependency in the project settings.  I added my dependencies in both the Dependencies tab in the build settings as well as under advanced settings->project references.

- would you be able to zip and send the projects so that I can try here?  As mentioned, I do not see the same issue.  You can also send the files offline via a friend/conversation request.   You should see my ID is also a link.

Best Regards,
Lisa

Hi Lisa,

i'm facing the same problem. Its only occurs when the referenced project is located under some subdir.

In order to reproduce you can make 2 projects:

1. Exe - under C:\Test\Exe

2. Lib - under C:\Test\SubDir\Lib

Make a reference/dependency from Exe to Lib (i.e. Exe depends on Lib) and save the projects

Now open a new workspace and import Exe while selecting to automatically import referenced projects.

You should get this error.

Thanks,

Assaf.

Hi David,

Could you please confirm that your set up matches the simplified set up shown in Assaf's post above?

CCS projects reference each other by name alone, i.e. they do not store any paths to the referenced projects.  So CCS has to perform a search to find the referenced projects during import.  Currently, CCS simply searches the parent directory of the main project (without recursing into subdirectories).  

I can make Assaf's example work by recursing into subdirectories.  But based on your screenshot, i cannot tell if that would work for you or not.  Let me know if that would work for you.

Thanks,

- Baltasar

There is an open bug for this: SDSCM00049202

Hi,

My projects are not all in the parent directory of the main project, however the referenced projects are not in sub-directories of the main project either (although they do have a common parent)

Example:

Main project: C:\Users\User\Desktop\TFS\FW 5900\DSP\APPS\EM MAIN\5900 EM MAIN

Referenced project: C:\Users\User\Desktop\TFS\FW 5900\DSP\LIBS\NDK\src\os\NDKOS

David,

I've implemented a fix which will be available in the upcoming CCS v6.  CCS would now search for the referenced projects in the same search-directory that you've selected when searching for the main project.  So, as long as your search-directory is high enough to encompass both the main project and the referenced projects, the referenced projects would be imported automatically.

The wizard's UI has been tweaked to make this behaviour more clear.

Thanks,

- Baltasar

Baltasar,
    I'm glad to hear this issue is being addressed as it has been causing me significant issues.

Is there a good reason why the referenced project can't be imported based on the project path? I have several instances where specifying a common search path would involve a scope of several hundred projects - some of which have duplicate names. If the referenced projects were imported based on full (or relative) paths to the main project it would resolve the issue in all cases, rather than in the specific case of all referenced projects sharing a common base directory.