search

calebkleveter / Mist

A CMS built with Vapor
MIT License
1 stars 0 forks source link

Request: For more specific instructions for build #1

Open mhamson opened 7 years ago

mhamson commented 7 years ago

I am having issue with building Mist. It would be nice to have a more precise step-by-step instructions, environment conditions, and nuisances to watch for. (clibressl might be one point of contention, but I am not sure why since I have built it in other projects without issue.)

calebkleveter commented 7 years ago

What issue are you coming across? There is a known issue that Vapor 2 projects are not compatible with Vapor 1 projects. All the dependencies but this one are on Vapor 2. Because that package is not yet using Vapor 2, it will cause package fetching to go into an infinite loop. Once that package is updated, I will finish updating Mist to Vapor 2.

I will cover setting up Mist in greater detail in the README when I get a chance, but for now, a lot of things you need to know are in this packages README.

mhamson commented 7 years ago

I can get around some issues with packages by doing a vapor fetch prior to swift build. The problem I have is with mysql…. I will add this to the issue… but here it is as well.

ld: library not found for -lmysqlclient for architecture x86_64

:0: error: link command failed with exit code 1 (use -v to see invocation) :0: error: build had 1 command failures error: exit(1): /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-build-tool -f /Users/Shared/VaporProjects/Mist/.build/debug.yaml I have drawn nada from google on how to get around this. > On 10 Jul 2017, at 16:40, Caleb Kleveter wrote: > > What issue are you coming across? There is a known issue that Vapor 2 projects are not compatible with Vapor 1 projects. All the dependencies but this one are on Vapor 2. Because that package is not yet using Vapor 2, it will cause package fetching to go into an infinite loop. Once that package is update, I will finish updating Mist to Vapor 2. > > I will cover setting up Mist in greater detail in the README when I get a chance, but for now, a lot of things you need to know are in this packages README . > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub , or mute the thread . >
calebkleveter commented 7 years ago

The current version of mist uses Vapor 1.5. I am working on updating it right now. You should here about this later today.

mhamson commented 7 years ago

Thank you Caleb!!!

On 10 Jul 2017, at 17:02, Caleb Kleveter notifications@github.com wrote:

The current version of mist uses Vapor 1.5. I am working on updating it right now. You should here about this later today.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/calebkleveter/Mist/issues/1#issuecomment-314133759, or mute the thread https://github.com/notifications/unsubscribe-auth/AACPcsEzr8jVVEyNnJewszPWPoRLjH5uks5sMj0cgaJpZM4OS7i-.

calebkleveter commented 7 years ago

I updated the Package.swift. In theory it should work now, but I am still having issues. I will get back to this latter. I am getting a little foggy brained.

mhamson commented 7 years ago

Caleb - thanks and completely understand

On 10 Jul 2017, at 20:44, Caleb Kleveter notifications@github.com wrote:

I updated the Package.swift. In theory it should work now, but I am still having issues. I will get back to this latter. I am getting a little foggy brained.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/calebkleveter/Mist/issues/1#issuecomment-314198152, or mute the thread https://github.com/notifications/unsubscribe-auth/AACPcui3-ZTTuWw59wTdYaXzl4pAMwSwks5sMnD0gaJpZM4OS7i-.