User forums > Help

The path contains too many '..' - annoying warning

(1/2) > >>

PMike:
I have a lot of files with relative paths (therefore, they contain "..\.." in its path). C::B drops error every time I open my workspace. So, I have two questions:
1. Why this warning is being dropped? C::B work fine after that
2. How to remove these warnings?

MortenMacFly:
Just a note: This message is generated by the underlying wxWidgets at:
[wxWidgets]/src/common/filename.cpp:966 (as of version 2.6.1).
I had this error as well and I replaced the relative path to the library that causes this errror (in my case!) with a direct one configured by a custom variable.

Morten.

PMike:
Custom variable is not an option for me, since I've to place workspace in different dirs on different machines. So, relative paths is my preference.

Urxae:

--- Quote from: PMike on November 07, 2005, 10:44:09 am ---Custom variable is not an option for me, since I've to place workspace in different dirs on different machines. So, relative paths is my preference.

--- End quote ---

Ehm, you realize you can set variables on a per-machine basis as well, right? (Settings -> Compiler -> Custom variables)
If you're using the CVS version, Global User Variables are probably an even better idea because they produce a prompt on opening the project asking what their value should be if they haven't been set yet.

thomas:

--- Quote from: Urxae on November 07, 2005, 11:01:30 am ---Ehm, you realize you can set variables on a per-machine basis as well, right? (Settings -> Compiler -> Custom variables)
--- End quote ---
Before you start modifying a dozen projects of yours, please note that global compiler variables are a new (experimental) feature which has only been in CVS for 10 days. At the present time, we are still testing it.

Although rather unlikely, it is still possible that we find an issue which forces us to modify the syntax of global user variables. This has already happened once during the last week when the scope resolution operator had to be changed from "::" to "#".
If you start using gcv in dozens of projects now and we change the syntax tomorrow, you will have to modify all of your projects again.

When we are confident that you will not blow away your foot using gcv, documentation on how to use them correctly will be released.

Navigation

[0] Message Index

[#] Next page