Talk:Portable Projects

Comments on Portable Projects -

Pensive.mb said ...
Is there a way I can use only one variable to specify the linked resource and the compiler linker options.

The path variable only takes an absolute path, I tried specifying the include path in terms of his absolute path variable but it gave me errors of not being able to resolved it

--Pensive.mb 18:16, 13 April 2009 (UTC)

Kishor.j said ...
Define file macros.ini in Project root path and you can set relative path in this file. It automatically gets imported when project is imported

--Kishor.j 07:01, 24 November 2010 (CST)

Drowley7474 said ...
I'm doing all of the above and I think I understand it. I'm adding a macros.ini file I believe in the correct place for the project (same directory position as the ".project" file). Then when I do what is under the heading above "Adding a single linked file" and then click on "Variables" the variable I added in macros.ini does not show up (I even restarted the PC). Should it? The way I read the above it should show up so I'm wondering if I'm doing something wrong or if I need to edit the .projects file by hand to add the relative path from the macros.ini file?

--Drowley7474 08:34, 21 June 2011 (CDT)

Drowley7474 said ...
I'm commenting on my own comment. I found sort of a subtle difference here.

The comment below applied to a workspace in "..\My Document\workspace6713" and the variable didn't show up as described. I've found that CCS really seems to like ..\My Documents\workspace so I created ..\My Documents\workspace\workspace6713 and using the macros.ini file in that condition and then I could see the Varible I added in macros.ini. And when I go and look at the linked file in ".projects" it adds the relative path as I expect.

--Drowley7474 09:16, 21 June 2011 (CDT)

Drowley7474 said ...
Changing the story again. I don't think the problem was it didn't like ..\My Documents\workspace6713. The problem appears to be the macros.ini file is only read when a workspace is "File->import"ed. So I added macros.ini and the workspace had been imported. So to get a workspace to recognize macros.ini changes; right click on the project in the project viewer and say DELETE (and keep the source code!!!). Then, if you haven't already, edit macros.ini. Then do File->import and it will use the changes to the macros.ini. At least that seems to work for me.

--Drowley7474 11:34, 21 June 2011 (CDT)