Foundry376/Mailspring
1
1
Fork 0
mirror of https://github.com/Foundry376/Mailspring.git synced 2025-01-06 08:08:10 +08:00
Code Issues Projects Releases Packages Wiki Activity
Mailspring/docs-atom/build-instructions/windows.md
Ben Gotow df38008c56 fix(*): Small fixes from Lake Tahoe. See Summary. 
Summary:
This diff includes a few small things:

- Menu: Don't select the first item until the user taps down arrow, and allow the user to use the arrow keys to move up and down through Menu items.

- Menu: Make scroll code from MultiselectList re-usable, use in Menu. Now if you use the keys to move to an item that is offscreen it will follow.

- Popover: Tapping the button that opened popover should close it

- Make sure buttons in toolbars are at least standard height

- Re-enable Markdown processing via `grunt docs`

- A bit of initial inline documentation for crosjdoc. Need to evaluate whether this is worth doing everywhere.

- New `search-playground` package for experimenting with search and search weights.

- Swap itemClassProvider for more generic itemPropProvider

- Add crojsdoc config file

- Export React, because third party packages can't require things from our app

- [FEATURE] Bring back static file support in third party packages via `nylas://translate/IMG_20150417_124142.jpg`

- Fix invariant error with search bar

- [FEATURE] "Show Original" under Message actions

- Fix DatabaseView so that many archives at once don't cause problems

Test Plan: Run specs

Reviewers: evan

Reviewed By: evan

Differential Revision: https://review.inboxapp.com/D1426
2015-04-22 16:41:29 -07:00

4.1 KiB
Raw Blame History

Windows

Requirements

On Windows 7

On Windows 8

Instructions

# Use the `Git Shell` app which was installed by GitHub for Windows. Also Make
# sure you have logged into the GitHub for Windows GUI App.
cd C:\
git clone https://github.com/inboxapp/edgehill/
cd edgehill
script/build # Creates application in the `Program Files` directory

Why do I have to use GitHub for Windows?

You don't. You can use your existing Git! GitHub for Windows's Git Shell is just easier to set up.

If you prefer using your existing Git installation, make sure git's cmd directory is in your PATH env variable (e.g. C:\Program Files (x86)\Git\cmd) before you open your powershell or command window. Note that you may have to open your command window as administrator. For powershell that doesn't seem to always be the case, though.

If none of this works, do install Github for Windows and use its Git shell. Makes life easier.

Troubleshooting

Common Errors

  • node is not recognized

    • If you just installed node you need to restart your computer before node is available on your Path.

  • script/build outputs only the Node and Python versions before returning

    • Try moving the repository to C:\atom. Most likely, the path is too long. See issue #2200.

  • error MSB4025: The project file could not be loaded. Invalid character in the given encoding.

  • script/build stops at installing runas with 'Failed at the runas@0.5.4 install script.'

    See the next item.

  • error MSB8020: The build tools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found.

    • If you're building atom with Visual Studio 2013 try executing the following command in your Git shell and then re-run script/build:

      $env:GYP_MSVS_VERSION=2013

  • Other node-gyp errors on first build attempt, even though the right node and python versions are installed.

    • Do try the build command one more time, as experience shows it often works on second try in many of these cases.

Windows build error reports in atom/atom

  • If all fails, use this search to get a list of reports about build errors on Windows, and see if yours has already been reported.

  • If it hasn't, please open a new issue with your Windows version 32/64bit and a print/screenshot of your build output, incl. the node and python versions.