Error Copying and renaming projects

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Luis Digital on Wed Oct 06 11:52:47 MST 2010
Hello CodeRed,

After you copy (and Paste) or rename a project, the IDE does not update the file path (Include paths), causing an error when compiling.

LPCXpresso Linux Beta 2

Thank you.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Oct 06 13:33:23 MST 2010

Quote: Luis Digital
Exactly, I am copying/renaming, and then modifying the examples.

For examples:
"${workspace_loc:/usbhid/inc}"

[COLOR=#000000]"usbhid" [/COLOR]should be changed to the new name of the project using a variable or a relative path, as you said.

That is an NXP controlled project, rather than a CodeRed one.

However having the tools automatically modify an include path in the way you suggest would probably not be a good idea (even if it were possible). If you consider a typical project, it might actually have multiple include paths which are workspace-based, for example if it is using library projects. Causing a include path name change could actually cause more problems than it would solve.

Thus I would suggest that when you encounter such problems when copying a project, you simply manually fix the include path to be relative.

Quote: Luis Digital
Some items are restricted:
"You are not authorized to view this page." (In Spanish)

Sorry. The "Copying Projects" FAQ should now be accessible.

Regards,
CodeRedSupport

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Luis Digital on Wed Oct 06 13:16:54 MST 2010

Quote:
There is also an FAQ on copying projects that might be of interest, though it doesn't cover the above include path issue:

http://support.code-red-tech.com/Cod...xampleProjects

Some items are restricted:
"You are not authorized to view this page." (In Spanish)

OK. Fixed. Thank you. :)

lpcware · ‎06-15-2016

Content originally posted in LPCWare by Luis Digital on Wed Oct 06 13:02:49 MST 2010

Quote:
[We recognize that there might still the odd Code Red produced example project that still references the include path via the absolute method, though we have been trying to fix these as we spot them]

Exactly, I am copying/renaming, and then modifying the examples.

For examples:
"${workspace_loc:/usbhid/inc}"

[COLOR=#000000]"usbhid" [/COLOR]should be changed to the new name of the project using a variable or a relative path, as you said.

Thank you.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by CodeRedSupport on Wed Oct 06 12:40:10 MST 2010
Do you mean include paths where the path points to inside the project itself? In this case, we would recommend that you use relative paths rather than absolute paths. Thus for example if you have a workspace thus

workspace
 + proj1
     - inc
     - src

If the source files within src use headers from the inc directory, then you should set up the include path as [FONT=Courier New][SIZE=1]../inc[/SIZE][/FONT] rather than [FONT=Courier New][SIZE=1]workspace/proj1/inc[/SIZE][/FONT].

[We recognize that there might still the odd Code Red produced example project that still references the include path via the absolute method, though we have been trying to fix these as we spot them]

There is also an FAQ on copying projects that might be of interest, though it doesn't cover the above include path issue:

http://support.code-red-tech.com/CodeRedWiki/CopyingExampleProjects

Regards,
CodeRedSupport