Git Product home page Git Product logo

Comments (17)

vzsg avatar vzsg commented on May 18, 2024 1

Or as an alternative, you could stick with the 0.8 version of the library if you don't want to make the jump to Vapor 2's alpha.

from jwt.

tanner0101 avatar tanner0101 commented on May 18, 2024

EDITED:

See https://stackoverflow.com/questions/43070534/openssl-ctls-trouble-with-vapor-2

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

eval "$(curl -sL openssl.vapor.sh)"
give me Swift 3.1 is required.

but
curl -sL check.vapor.sh | bash

tel me it's ok. Hw can I upgrade my tool chain ? Xcode is up to date

from jwt.

tanner0101 avatar tanner0101 commented on May 18, 2024

This package uses Vapor 2. That script is for Vapor 1.

eval "$(curl -sL check2.vapor.sh)"

You'll need to either:

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

Thanks you for your answer gonna try to update those and try agin

from jwt.

tanner0101 avatar tanner0101 commented on May 18, 2024

You may also need to add this to your bash profile:

export TOOLCHAINS=swift

That will make the terminal use the latest version of Swift on your computer. You can test to see if it's using Swift 3.1 with swift --version

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

After export TOOLCHAINS=swift, swift --version still give me 3.0.2. I'm upgrading so I can move to Vapor 2 as I was experiencing some compatibility issues with some providers. Is jwt-provider ready for Vapor 2 ?

I'm building a bearer auth system based on jwt.

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

I've installed Xcode 8.3 beta 4, selected the beta with Xcode-select. Both scripts seems to perform ok :

eval "$(curl -sL openssl.vapor.sh)" 
✅  Compatible with Vapor 2
✅  OpenSSL available
 eval "$(curl -sL check2.vapor.sh)"
✅  Compatible with Vapor 2
swift --version
Apple Swift version 3.1 (swiftlang-802.0.42.1 clang-802.0.36)
Target: x86_64-apple-macosx10.9

So everything should work but I still have the same error. Also tried couple things like clean, rebuilt etc..

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

Tried to clone again the project as I may have broken something but same result
Also updated vapor with vapor self update

from jwt.

tanner0101 avatar tanner0101 commented on May 18, 2024

EDITED:

See: https://stackoverflow.com/questions/43070534/openssl-ctls-trouble-with-vapor-2

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

I've restarted my computer, downloaded a fresh version of the repo, got all the scripts to say it's ok but it's always stuck at compile time.

from jwt.

tanner0101 avatar tanner0101 commented on May 18, 2024

Can you paste me the output of the following two commands on your computer:

Gyda:~ tanner$ pkg-config openssl --cflags
-I/usr/local/opt/openssl/include
Gyda:~ tanner$ pkg-config openssl --libs
-L/usr/local/opt/openssl/lib -lssl -lcrypto -lz -lcrypto -lz

Additionally, is it the same error Could not build Objective-C module 'CTLS' from above or a different one?

from jwt.

ryan-luas avatar ryan-luas commented on May 18, 2024

@Alex293 https://github.com/kylef/swiftenv is a great tool for managing your swift version & tool chain. Often you can set the tool chain in Xcode preferences, however that doesn't switch the one used in your shell environment... so that's a great tool to view and switch quickly.

from jwt.

Alex293 avatar Alex293 commented on May 18, 2024

Did the had time to test but avec the last Xcode it should ok I think

from jwt.

BrettRToomey avatar BrettRToomey commented on May 18, 2024

Closing due to inactivity. Please feel free to reopen.

from jwt.

ryanmjt avatar ryanmjt commented on May 18, 2024

I am running into this issue now. I have the latest Xcode installed (8.3.2) along with CLI tools and vapor (2.0.3) installed from homebrew tap. swift --version says 3.1.

The only thing "special" about my setup is that homebrew is installed to a non-standard location (i.e. not /usr/local).

Edit, the output:

> pkg-config openssl --cflags

> pkg-config openssl --libs
-lssl -lcrypto -lz

Edit 2:

If I manually specify -Xswiftc -I ... -Xlinker -L ... to my brew info openssl paths it works. Is there a way to set this in some config or something so I don't have to do this for every build?

Since my machine has a custom path I don't want to commit these paths up to the repository.

from jwt.

jhoughjr avatar jhoughjr commented on May 18, 2024

Still an issue on ARM. Hypriot 1.5 Swift 3.1.1

from jwt.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.