Groot fails to be linked when using Xcode7.1 with Carthage

[scriptease]

Hello,

there seems to be a problem with the binary version that is attached to the current tag.
It can not be linked in Xcode 7.1

My solution for now is to let Carthage build the library instead of downloading it.

  $ carthage update --platform iOS --no-use-binaries

Maybe someone has the same issue :-)

Kind regards,
Florian

[gonzalezreal]

Hi @scriptease

What kind of errors are you getting? Could you please paste the output log?

Thanks,
Guille

[scriptease]

/Volumes/XXX/XXX/XXX/Model/Database.swift:12:8: Module file was created by an older version of the compiler; rebuild 'Groot' and try again: /Users/xxx/Library/Developer/Xcode/DerivedData/XXX-fswyylxndaveorcrcizcjioeyfvk/Build/Products/Debug-iphonesimulator/Groot.framework/Modules/Groot.swiftmodule/x86_64.swiftmodule

I hope this helps

[tehprofessor]

I had the same issue, but if I build from master it works*. It did, when building from master, complain about some missing SDKs.

*** Fetching Groot
*** Checking out Groot at "8987279d1ea39a1a5e30b59a5f7751f49d5ac5e0"
*** xcodebuild output can be found in /var/folders/5g/bjx_pdsn5nbdxyvtnc30sjm40000gn/T/carthage-xcodebuild.QvIV6i.log
*** Building scheme "Groot-Mac" in Groot.xcodeproj
*** Building scheme "Groot" in Groot.xcodeproj
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/Developer/Library/Frameworks'
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS9.2.sdk/Developer/Library/Frameworks'
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/Developer/Library/Frameworks'
ld: warning: directory not found for option '-F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator9.2.sdk/Developer/Library/Frameworks'

• I think (it works)... I am about to actually use it; as I was writing a comment to say "I had the same issue"