WIP: Compile on windows #891
No reviewers
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#891
Loading…
Reference in a new issue
No description provided.
Delete branch "michael/garage:mzhang/windows-build"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Still WIP, I still need to do some research into how to achieve a similar effect as the permissions-setting part that I commented out, but this now builds on Windows.
I'm going to try to add the Windows node into my Garage cluster to see how it fares.
Something important to note is that on Windows, libpnet requires the additional library npcap for Packet.lib.
I don't know how to automate building any of this yet, but for now I just got rid of the compile errors from unix-specific features
Remaining TODOs:
9ee1231e5b
to03e954560e
The file size thing still frequently reports
?
for the windows build. will investigate laterI think we can ignore this on Windows for now. The "correct" solution would probably be to use NT ACLs to restrict read access to the secret key, but I think we can just leave this for later and for now just not do anything particular when running on Windows. Also, it's probably not necessary to set the readonly attribute, we can just skip this and make the code simpler.
We can also keep this for later as an open issue if you want this PR to be merged as is.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.