Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating and compiling default Playground works but inform that "fails" in macOS 10.14 #122

Closed
dfreniche opened this issue Feb 4, 2020 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@dfreniche
Copy link

I'm in macOS 10.14.6. Don't ask coughAppceleratorcough

To replicate:

$ nef playground --name test                                   
Installing Playground (test)... ✅
Set test target to iOS ✅
Updating version (0.7.0)... ✅
Installing Pods ... ✅
$ nef compile test.app              
Installing Pods ... ✅
Building test (test) ... ✅
Copy frameworks ✅
Found 1 playgrounds
   Compiling page.xcplaygroundpage ...<unknown>:0: error: Swift does not support the SDK 'MacOSX10.14.sdk'

If you open test.app and compile, all is OK.

So although we get that error message, seems like it's compiling OK and also can generate markdown fine.

@miguelangel-dev
Copy link
Member

miguelangel-dev commented Feb 4, 2020

Nice! Thanks for testing nef - the best QA!!

In fact, nef is compatible with macos 10.14+. Could you attach the log?

  1. test.app/nef/log/page.log to get more information about the page compilation
  2. test.app/nef/log/test.log to get more information about the project compilation
  3. you can find the file used to build in test.app/nef/build/page/main.swift

Thanks! ^^

@miguelangel-dev
Copy link
Member

miguelangel-dev commented Feb 4, 2020

And about the render mode: jekyll, carbon, markdown... works independently the compilation step. You can generate code without verifying it before.

Compile step let you in CI (for example) keeps aligned the documentation into your lib, or post...

@miguelangel-dev miguelangel-dev added the bug Something isn't working label Feb 4, 2020
@miguelangel-dev miguelangel-dev self-assigned this Feb 4, 2020
@miguelangel-dev
Copy link
Member

It'll be solved in this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants