Pailead cannot be built --no-use-binaries on Carthage about pailead HOT 9 OPEN

Please verify using
Pailead.framework.zip

from pailead.

The library works fine, the issue is with the Carthage distribution.

From the Carthage docs:

Carthage will only build Xcode schemes that are shared from your .xcodeproj. You can see if all of your intended schemes build successfully by running carthage build --no-skip-current, then checking the Carthage/Build folder.

If an important scheme is not built when you run that command, open Xcode and make sure that the scheme is marked as Shared, so Carthage can discover it.

You can choose to distribute you're library as binary only, Pailead is not currently distributed as binary only so if you list it in the dependencies of your project and add --no-use-binaries dependencies will not resolve.

from pailead.

Pailead is distributed with the binary in the Github release.

from pailead.

Can you please check this log. I use SPM and misconfigured the Shared config (I used the default but this has no library) so I fixed it and was wondering if you could please try using that framework zip before I push it.

from pailead.

Sure does this framework contain the fix in #2 I can test them both at once? (I'm on the same project as @ValCanBuild) I'm not sure I can verify this bug with just a framework. As it part of the Carthage bootstrap process.

from pailead.

I’m assuming this works. (And it should you can use path instead of github in you Cartfile)

_{Sent with GitHawk}

from pailead.

Thanks for the fix, I tested the framework by just unzipping it and dropping it into the build folder.

Using path to the binary won't allow me to test it this bug. It doesn't allow me to build from binary.

With other binary only frameworks Carthage doesn't try to build them it skips the build process and prints a message. I'll test when the new build is out :)

from pailead.

Releasing it in a few hours, thanks for the patience busy week.

from pailead.

@pducks32 is this now released?

from pailead.