Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Neuroglancer on Windows 10 #12

Closed
Kaju-Bubanja opened this issue Jan 3, 2017 · 2 comments
Closed

Neuroglancer on Windows 10 #12

Kaju-Bubanja opened this issue Jan 3, 2017 · 2 comments
Labels

Comments

@Kaju-Bubanja
Copy link

I'm trying to build and run neuroglancer on windows 10 64bit, but was not able to build it.
I tried following the instructions given with nodejs versions 5.9.0, 6.1.0, 7.2.0 and 7.3.0.
With all versions npm complains that the fsevents module could not be installed:
notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
I assume that this is important, because when trying to run the dev server it complains about two things:

  1. ts-loader: \neuroglancer\config\typescript_compiler_shim.js@2.1.4. This version may or may not be compatible with ts-loader.
  2. ERROR in error TS18002: The 'files' list in config file 'tsconfig.json' is empty.
    What files do need to be specified in the tsconfig?
    And is it even possible to get neuroglancer running on windows?
@jbms
Copy link
Collaborator

jbms commented Jan 3, 2017

Thanks for reporting this issue. I don't think there should be any fundamental problem that prevents it from building on Windows, but so far the build process has only been tested on Linux and Mac OS. The fsevents and ts-loader warnings are expected and can be ignored --- the real error appears to be related to the 'files' list. I will see if I can reproduce the problem in a Windows environment and get back to you. Neuroglancer should run fine in Chrome and Firefox on Windows. It doesn't yet work on Microsoft Edge due to Edge lacking support for the WEBGL_draw_buffers extension that is used by Neuroglancer --- a workaround is possible, at some performance cost in certain cases, but has not yet been implemented.

@jbms jbms added the bug label Jan 3, 2017
@jbms
Copy link
Collaborator

jbms commented Jan 3, 2017

There was a bug in how the configuration scripts were specifying the path to the tsconfig.json file; it happened to work accidentally on Linux and Mac OS, but did not work on Windows. I've now fixed it and confirmed that both the build and dev-server actions now work on Windows.

@jbms jbms closed this as completed Jan 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants