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.
Hi,
We are sharing a project through a source control application (Perforce) and to make it portable, each project has its macros.ini file which defines relative paths necessary for it to build (see attached file).
On my computer (Windows 7), when I import a project from the source control application, the macros are correctly assigned in the Preferences -> General -> Workspace -> Linked Resources window. Then, I can correctly build the project.
On my colleague's computer (Windows Vista), when we import the same project, the macros are not assigned in that same window. Moreover, even if I manually create them in that window, they are not reflected in the project. In order to make the project work as expected, I need to go inside the project build options and create the macros there.
Is there something wrong with the way we are proceeding?
Thanks
Franck
What version of CCS are you and your colleague using?
What method are you and your colleague using to import the project? is it being done via File->Import-> General-> Existing Projects into Workspace, or via Project-> Import Existing CCS/CCE Eclipse Project?
I am told that in CCS 4.1.3, the File->Import-> General-> Existing Projects into Workspace wizard does not handle the macros at all. The preferred method is to use Project-> Import Existing CCS/CCE Eclipse Project. If the File->Import method is used, then they can manually import the macros.ini file using the File->Import-> CCS-> Managed Build Macros wizard.
Actually, I was using the import method provided by the Perforce Eclipse plug-in. You are right, if I use the Project -> Import Existing CCS/CCE Eclipse Project button, everything works as expected. We will proceed that way in the future.
Thank you for your help.
Franck