serde/appveyor.yml

environment:
  matrix:
    - APPVEYOR_RUST_CHANNEL: stable
    - APPVEYOR_RUST_CHANNEL: nightly

install:
  # Install rust, x86_64-pc-windows-msvc host
  - curl -sSf -o rustup-init.exe https://win.rustup.rs/
  - rustup-init.exe -y --default-host x86_64-pc-windows-msvc --default-toolchain %APPVEYOR_RUST_CHANNEL%
  - set PATH=C:\msys64\usr\bin;%PATH%;C:\Users\appveyor\.cargo\bin
  - rustc -vV
  - cargo -vV

build: false

test_script:
  - sh -c 'PATH=`rustc --print sysroot`/bin:$PATH ./travis.sh'
Implement Serialize/Deserialize for OsStr/OsString This commit implements the two serde traits for the libstd `OsStr` and `OsString` types. This came up as a use case during implementing sccache where we're basically just doing IPC to communicate paths around. Additionally the `Path` and `PathBuf` implementations have been updated to delegate to the os string ones. These types are platform-specific, however, so the serialization/deserialization isn't trivial. Currently this "fakes" a newtype variant for Unix/Windows to prevent cross-platform serialization/deserialization. This means if you're doing IPC within the same OS (e.g. Windows to Windows) then serialization should be infallible. If you're doing IPC across platforms (e.g. Unix to Windows) then using `OsString` is guaranteed to fail as bytes from one OS won't deserialize on the other (even if they're unicode). 2017-03-27 11:15:22 -05:00			`environment:`
			`matrix:`
			`- APPVEYOR_RUST_CHANNEL: stable`
			`- APPVEYOR_RUST_CHANNEL: nightly`

			`install:`
			`# Install rust, x86_64-pc-windows-msvc host`
get rustup-init with curl to avoid tls failures 2018-01-04 22:04:16 -06:00			`- curl -sSf -o rustup-init.exe https://win.rustup.rs/`
Implement Serialize/Deserialize for OsStr/OsString This commit implements the two serde traits for the libstd `OsStr` and `OsString` types. This came up as a use case during implementing sccache where we're basically just doing IPC to communicate paths around. Additionally the `Path` and `PathBuf` implementations have been updated to delegate to the os string ones. These types are platform-specific, however, so the serialization/deserialization isn't trivial. Currently this "fakes" a newtype variant for Unix/Windows to prevent cross-platform serialization/deserialization. This means if you're doing IPC within the same OS (e.g. Windows to Windows) then serialization should be infallible. If you're doing IPC across platforms (e.g. Unix to Windows) then using `OsString` is guaranteed to fail as bytes from one OS won't deserialize on the other (even if they're unicode). 2017-03-27 11:15:22 -05:00			`- rustup-init.exe -y --default-host x86_64-pc-windows-msvc --default-toolchain %APPVEYOR_RUST_CHANNEL%`
			`- set PATH=C:\msys64\usr\bin;%PATH%;C:\Users\appveyor\.cargo\bin`
			`- rustc -vV`
			`- cargo -vV`

			`build: false`

			`test_script:`
			- sh -c 'PATH=`rustc --print sysroot`/bin:$PATH ./travis.sh'