about summary refs log tree commit diff
path: root/src/test/run-pass/thinlto
diff options
context:
space:
mode:
authorCorey Farwell <coreyf@rwell.org>2017-02-05 09:14:36 -0500
committerGitHub <noreply@github.com>2017-02-05 09:14:36 -0500
commit6a4c906f7ab30300b1792cb7a24a1e326fd01aec (patch)
tree3c5a63acbdc0ba896c9b8a371b850272862080f9 /src/test/run-pass/thinlto
parent001bfb9e566b92b9336eb210b270c9404626d89f (diff)
parent02ae1e10605dccf29c77f94dbbf916b28d2b7c54 (diff)
downloadrust-6a4c906f7ab30300b1792cb7a24a1e326fd01aec.tar.gz
rust-6a4c906f7ab30300b1792cb7a24a1e326fd01aec.zip
Rollup merge of #38921 - chris-morgan:windows-unprivileged-symlink-creation, r=alexcrichton
Support unprivileged symlink creation in Windows

Symlink creation on Windows has in the past basically required admin; it’s being opened up a bit in the Creators Update, so that at least people who have put their computers into Developer Mode will be able to create symlinks without special privileges. (It’s unclear from what Microsoft has said whether Developer Mode will be required in the final Creators Update release, but sadly I expect it still will be, so this *still* won’t be as helpful as I’d like.)

Because of compatibility concerns, they’ve hidden this new functionality behind a new flag in the CreateSymbolicLink dwFlags: `SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE`. So we add this flag in order to join the party.

Sources:

- https://blogs.windows.com/buildingapps/2016/12/02/symlinks-windows-10/ is the official announcement (search for CreateSymbolicLink)

- https://news.ycombinator.com/item?id=13096354 on why the new flag.
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions