Jucer PC to Mac transfer wierdness


#1

Not Working
Project created from PC and then copied to Mac using latest projucer fails to compile on Xcode.

Example error (of many): /Users/jim/Code/phase-correlation-meter/JuceLibraryCode/juce_audio_basics.mm:9:10: fatal error: ‘juce_audio_basics/juce_audio_basics.mm’ file not found

Has -I …/…/…/juce.latest/ in compiler log

Working
Project created from Mac using latest projucer:
Has -I…/…/…/…/juce.latest/modules

And compiles okay.

Also
I’m getting a lot of assertations on the console about juce::File when I open up Projucer.


#2

Ah - problem solved:

The JUCER allows …/juce or …/juce/modules and shows both as correct as a module path. However only the latter will build a project. The former almost works but actually needs to report an error in the JUCER. Suggest that there’s a minor fix required here :wink:


#3

JUCE Assertion failure in juce_File.cpp:174
Illegal absolute path: extras/Projucer/Builds/MacOSX/build/Debug/Projucer.app/Contents/MacOS/Projucer

This isn’t supposed to appear tho:)


#4

OK. This is finally fixed now on the develop branch. Thanks for reporting.


#5

Did you fix both problems? :slight_smile:


#6

Can you provide a stack trace for the assertion in juce File?


#7

Try specifying a jucer file on the command line using a relative path? If you don’t get the error then - let me know and I’ll sort a trace…