-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
self commands, including compile #10
Conversation
…ary at the given path (default `$CWD`)
do { | ||
try run(cmd) | ||
} catch { | ||
fail("Could not compile \(src), try running the folloing command in order to debug this issue:\n\(cmd)") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo in following
This is a cool idea, I'm interested to see if it works on Linux as well. |
I’ll see if this can work on Linux as well. Don’t see why not, it’s just the |
… doesn't have a ".swift" extension: ``` ld: warning: ignoring file ./vapor-cli/vapor, file was built for unsupported file format ( 0x23 0x21 0x2F 0x75 0x73 0x72 0x2F 0x62 0x69 0x6E 0x2F 0x65 0x6E 0x76 0x20 0x73 ) which is not the architecture being linked (x86_64): ./vapor-cli/vapor Undefined symbols for architecture x86_64: "_main", referenced from: implicit entry/start for main executable ld: symbol(s) not found for architecture x86_64 ``` Therefore we'll need to rename the script to `vapor.swift`.
… with an already `bootstrapp`ed file
Halleluja |
|
Yeah, let's do |
I had a thought how we could solve the install step. What if on every launch the script checks (via |
bootstrap
command to compile vapor.swift
into binary
I noticed that the vapor-cli command was getting quite slow when working on the
docker
command so I added abootstrap
command that will compile and install a binaryvapor
at the given path (or $CWD).This should probably also be called automatically by
self-update
.