I just finished a bunch of development on os x. now when I open up the jucer file in windows 10 and save the project so I can work on the windows build, i get a ton of errors because all of the paths in the #includes are using Mac-style /'s.
juceHeader.h looks like this, which is appropriate if i were loading it up on OS X:
Any idea what is causing this? I don’t want to manually change EVERY header path in EVERY file my project uses. This seems like a very strange bug that shouldn’t happen…
As far as I know, the forward slash works on windows for relative paths too. You don’t need to change the paths. At least I had never problems with this format compiling on visual studio, although I couldn’t find backup for my claim searching the web…
Weird. My juce folder is located at ../JUCE-4.2.4/modules
It doesn’t cause a problem for me on OS X. should I be using a fixed path on windows? I’ve never had this problem before with other projects. I can’t remember if I was using fixed paths or relative paths tho…
It also doesn’t like my custom modules, located at
<matkatmusic_modules/matkatmusic_modules.h>
When I get home I’ll look at the exact errors in VS2013. But they all said
"can’t find file …" For each file in my juce_header.h