<!DOCTYPE html><htmllang="en"><head><metacharSet="utf-8"/><metahttp-equiv="X-UA-Compatible"content="IE=edge"/><title>windows-users · bitcoin-s</title><metaname="viewport"content="width=device-width, initial-scale=1.0"/><metaname="generator"content="Docusaurus"/><metaname="description"content="This will be a guide directed to Windows Users hoping to contribute to Bitcoin-s and its development."/><metaname="docsearch:version"content="1.9.2"/><metaname="docsearch:language"content="en"/><metaproperty="og:title"content="windows-users · bitcoin-s"/><metaproperty="og:type"content="website"/><metaproperty="og:url"content="https://bitcoin-s.org/"/><metaproperty="og:description"content="This will be a guide directed to Windows Users hoping to contribute to Bitcoin-s and its development."/><metaproperty="og:image"content="https://bitcoin-s.org/img/undraw_online.svg"/><metaname="twitter:card"content="summary"/><metaname="twitter:image"content="https://bitcoin-s.org/img/undraw_tweetstorm.svg"/><linkrel="shortcut icon"href="/img/favicon.ico"/><linkrel="stylesheet"href="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.css"/><linkrel="stylesheet"href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.12.0/styles/default.min.css"/><script>
</script><linkrel="stylesheet"href="/css/code-block-buttons.css"/><scripttype="text/javascript"src="https://buttons.github.io/buttons.js"></script><scripttype="text/javascript"src="https://cdnjs.cloudflare.com/ajax/libs/clipboard.js/2.0.0/clipboard.min.js"></script><scripttype="text/javascript"src="https://fonts.googleapis.com/css?family=Montserrat:500"></script><scripttype="text/javascript"src="https://www.googletagmanager.com/gtag/js?id=UA-61958686-2"></script><scripttype="text/javascript"src="/js/code-block-buttons.js"></script><scriptsrc="/js/scrollSpy.js"></script><linkrel="stylesheet"href="/css/main.css"/><scriptsrc="/js/codetabs.js"></script></head><bodyclass="sideNavVisible separateOnPageNav"><divclass="fixedHeaderContainer"><divclass="headerWrapper wrapper"><header><ahref="/"><imgclass="logo"src="/img/favicon.ico"alt="bitcoin-s"/><h2class="headerTitleWithLogo">bitcoin-s</h2></a><ahref="/versions"><h3>1.9.2</h3></a><divclass="navigationWrapper navigationSlider"><navclass="slidingNav"><ulclass="nav-site nav-site-internal"><liclass=""><ahref="/docs/core/core-intro"target="_self">Docs</a></li><liclass=""><ahref="/download"target="_self">Download</a></li><liclass=""><ahref="/api/org/bitcoins"target="_self">API</a></li><liclass=""><ahref="/help"target="_self">Help</a></li><liclass="navSearchWrapper reactNavSearchWrapper"><inputtype="text"id="search_input_react"placeholder="Search"title="Search"/></li></ul></nav></div></header></div></div><divclass="navPusher"><divclass="docMainWrapper wrapper"><divclass="container mainContainer docsContainer"><divclass="wrapper"><divclass="post"><headerclass="postHeader"><aclass="edit-page-link button"href="https://github.com/bitcoin-s/bitcoin-s/blob/master/docs/windows-users.md"target="_blank"rel="noreferrer noopener">Edit</a><h1id="__docusaurus"class="postHeaderTitle">windows-users</h1></header><article><div><span><p>This will be a guide directed to Windows Users hoping to contribute to Bitcoin-s and its development.</p>
<p>Reference the <code>contributing.md</code> document for a more descriptive guide on what bloop is and how to use it.
When following the installation guide to bloop on their website you will use <code>scoop</code> to install <code>bloop</code>. After installation
there will more than likely be issues with <code>bloop</code> looking for <code>.jar</code> files in a folder like <code>C:\root\.ivy2\</code>. The true installation
location of the <code>.ivy2</code> folder is likely in <code>C:\users\{your_username}\.ivy2\</code>. Once we have located our <code>.ivy2</code> folder
we will want to direct <code>bloop</code> on how to find the files in the new location. I found it was quite simple to use Windows
symbolic link (Note: if you are a running a Linux Subsystem this will also influence where your Linux bloop looks for this directory and thus will break as subsystems will have to use the <code>mnt</code> folder to access <code>C</code> drive).
the <code>/D</code> option specifies that it is a directory. You will need to run this command in <code>cmd.exe</code> instead of <code>Windows Powershell</code> as it is not a standalone executable.</p>
<p>Currently there are written changes in code to make it so you are run a node on Windows. Path specs are based on out of box installation. In the case you receive an error like <code>Could not locate bitcoind on user PATH</code>
then you will need to do some tweaking of either the code or moving your folder into the correct location. Currently this is specified by the <code>DEFAULT_DATADIR</code> in <code>BitcoindConfig</code> within <code>Bitcoind-rpc</code>. When you install bitcoin out of box there are 2 folders
created, 1 which is contained in the location on the wiki and that contains data generated after syncing. The current directory <code>DEFAULT_DATADIR</code> is pointing at which contains the <code>bitcoind.exe</code> file.
That file is what is necessary to start up a bitcoind node.</p>
<p>If you are looking to develop in a Linux environment on a Windows Machine I have had success with <ahref="https://docs.microsoft.com/en-us/windows/wsl/install-win10">Windows Subsystem for Linux (WSL)</a>.
If you are interested in working on both Linux and Windows for development reasons I would also recommend <ahref="https://github.com/microsoft/terminal">Windows Terminal</a> as a way to hold many different terminals all in one window including your</p>
<p>Linux distro if you set up a WSL. With that being said the most important thing to consider when running Linux on a Windows Machine while also developing on Windows, there will be differences in setting up directories and pathing especially for <code>bloop</code>. I will update if I find a functional workaround.
Currently trying to get bloop working on a WSL that already has linked folders to have bloop work on Windows. Linux cannot recognize the file paths for directories as they are in Windows format, trying to find a workaround.</p>
