I am defining a project in Projucer and filling the field VST/VST3 Folder field with ..\..\..\..\..\..\..\..\SDKs\VST\vstsdk2.4 (8 times back then SDKs\VST\vstdsk2.4)
For some reasons, when generating the project, I can see in VS "Additional Include Directory" field that 2 "..\" were added such the path is now:
..\..\..\..\..\..\..\..\..\..\SDKs\VST\vstsdk2.4, and it is a wrong path.
It'll adjust the path to be relative to the build folder that's generated. We use a lot of projects that rely on that path and haven't noticed a problem with it. Are you saying the project doesn't work?
Which path are you talking about? The one in the global settings should be absolute. And the one in the per-exporter project settings should be relative to the .jucer project you're using. Like I said, it gets adjusted to be relative to the build folder, you shouldn't enter it relaitve to that.
I have just understood what you meant, the path I need to enter is relative to the jucer file, and projucer will readjust it...
Still some issues:
1) It does not seem to work when I define that Target projet folder is the same as jucer file (I write a "."(dot) in the field). The project is generated at the right place, but I expect that in this configuration, VST paths will remain unchanged. Still it will add me one "..\"
2) The bahavior is not consistent for VST paths and "Header Search Path". In the latter, path won't be readjusted, and remained as entered.
Try rebuilding the introjucer with the very latest code, I fixed a parsing problem involving '.' paths today. But there's really no need for the dot, you can just leave it out.
For header search path fields, we don't mess with them because it'll tend to be custom paths.
It's probably the most widely used development tool in history. If you've heard of a thing called "google", then you might want to use that to search for it!