Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Create Windows build scripts and update instructions #1721
Having the information in a single location is conceptually simple, but maybe the other direction is better? That way it's available when you download the code and need to operate offline?…
On Wed, Jan 23, 2019 at 8:57 AM Jack Gerrits ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In README.Windows.md <#1721 (comment)> : > @@ -0,0 +1,41 @@ +## Windows specific info + +This document details differences in pre-requisites and building instructions under Windows. So the readme is a bit out of date at the moment, I've done work to try and make sure the wiki is up to date. I've utilized several pages in the wiki to make it a bit simpler. I was planning on making the front page readme a bit simpler and just using it to explain VW's mission and why use it, then link into the wiki for instructions — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1721 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE25gL73AYks4KS1BaQBQawEKbh-TMcks5vGGo-gaJpZM4aNTQ_> .
Totally agree, plus there's the added benefit of pull requests for changes when they are in files. So we can either migrate the existing wiki docs to a folder in the vowpalwabbit repo, or we can utilize the docs repo I recently created to host the rl_client docs. (See here https://vowpalwabbit.github.io/docs/, but this removes the benefit of automatically having it available locally for offline use) Or we can wait until the website is ready and think about how the pages fit in there? The wiki is useful for the sidebar aswell