-
Notifications
You must be signed in to change notification settings - Fork 105
fixes #180 : Enable syntax highlight to all platform #352
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,37 +1,39 @@ | ||
# Based on the "trust" template v0.1.1 | ||
# https://github.com/japaric/trust/tree/v0.1.1 | ||
|
||
os: Visual Studio 2017 | ||
|
||
environment: | ||
global: | ||
RUST_VERSION: stable | ||
CRATE_NAME: cobalt | ||
APPVEYOR_CACHE_SKIP_RESTORE: true | ||
|
||
matrix: | ||
# Stable channel | ||
- TARGET: x86_64-pc-windows-gnu | ||
CHANNEL: stable | ||
- TARGET: i686-pc-windows-msvc | ||
CHANNEL: stable | ||
- TARGET: x86_64-pc-windows-msvc | ||
CHANNEL: stable | ||
TOOLCHAIN: msvc | ||
|
||
# Beta channel | ||
- TARGET: x86_64-pc-windows-msvc | ||
CHANNEL: beta | ||
TOOLCHAIN: msvc | ||
|
||
install: | ||
- ps: >- | ||
$Env:PATH += ';C:\msys64\usr\bin' | ||
- if "%TOOLCHAIN%" == "msvc" call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvars64.bat" | ||
- if "%TOOLCHAIN%" == "msys" set PATH=C:\msys64\mingw%MSYS_BITS%\bin;C:\msys64\usr\bin;%PATH% | ||
- curl -sSf -o rustup-init.exe https://win.rustup.rs/ | ||
- rustup-init.exe -y --default-host %TARGET% --default-toolchain %RUST_VERSION% | ||
- rustup-init.exe -y --default-host %TARGET% --default-toolchain %CHANNEL% | ||
- set PATH=%PATH%;C:\Users\appveyor\.cargo\bin | ||
|
||
test_script: | ||
- rustc -Vv | ||
- cargo -V | ||
|
||
test_script: | ||
# we don't run the "test phase" when doing deploys | ||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo check --verbose ) | ||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo test --verbose ) | ||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo +%CHANNEL%-%TARGET% build ) | ||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo +%CHANNEL%-%TARGET% test ) | ||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo +%CHANNEL%-%TARGET% build --no-default-features ) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do these still need to be There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. As said on gitter: because of natives C/C++ libs we need the build as There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The annoying thing is that this doesn't seem to be a problem on Linux :( |
||
- if [%APPVEYOR_REPO_TAG%]==[false] ( cargo +%CHANNEL%-%TARGET% test --no-default-features ) | ||
|
||
before_deploy: | ||
- cargo rustc --target %TARGET% --release --bin cobalt -- -C lto | ||
|
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.
At some point we should make it so different feature combinations run as different jobs so they can run in parallel rather than series.
Granted that can get messy, particularly when we already have problems with our rustfmt and clippy jobs (see #305)
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.
Is this possible with travis?
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.
Yup, we just define more jobs in the matrix with a different variable set to control what happens in the job, maybe a
FEATURE
variable that is--feature "sass"
vs--no-default-features
.Not something to include in this because it'd require a lot more experimenting and we shouldn't hold this up :)