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

$ npm run build - in Windows #49

Open
skyview059 opened this issue Jan 4, 2016 · 11 comments
Open

$ npm run build - in Windows #49

skyview059 opened this issue Jan 4, 2016 · 11 comments

Comments

@skyview059
Copy link

Hi i'm new.
How can I build this for windows?? is it support windows or not? :)

Error message is bellow.

Kanny@DESKTOP-O2HSVSO ~/screencat (master)
$ npm run build

screencat@4.2.0 build c:\Users\Kanny\screencat
electron-packager . ScreenCat --platform=darwin --arch=x64 --version=0.36.0 --protocol-name="ScreenCat URL" --protocol="screencat" --ignore=node_modules/electron-prebuilt --ignore=node_modules/electron-packager --ignore=node_modules/browserify --ignore=node_modules/wzrd --ignore=node_modules/standard && cp img/Icon.icns ScreenCat.app/Contents/Resources/atom.icns

cp: cannot create regular file `ScreenCat.app/Contents/Resources/atom.icns': No such file or directory
npm ERR! weird error 1
npm ERR! not ok code 0

@max-mapper
Copy link
Owner

hi @skyview059, windows support is experimental but it was built last week successfully on windows by someone else. there are windows specific instructions here: https://github.com/maxogden/screencat#building-the-app

@eduardofg
Copy link

hi @maxogden, I tryed build in windows, but when executed (npm start), I get an error (in line 1 and char 1). Do you have any idea? Tks a lot

@mafintosh
Copy link
Collaborator

@eduardofg what's the error?

@eduardofg
Copy link

hi, @mafintosh, It's an error 800A138F, in electron.js, the same if you execute the .js manually.

@eduardofg
Copy link

Hi @mafintosh and @maxogden, I didn't had installed the electron runtime (sorry)(http://maxogden.com/electron-fundamentals.html). I started the electron.js but I not understand what the next step. I need start the app.js with node too? Thanks a lot

@carletto
Copy link

carletto commented Feb 8, 2016

I have the same error 800A138F in win 7 on npm start... How I fix? Thaks

@eduardofg
Copy link

hi @carletto. Install the prebuilt of electron (npm install electron-prebuilt -g), now the comand "electron" works. (electron electron.js), but out of directory "screencat". If you execute "electron" its open a new window, for you put the application. I dragged and drop the electron.js and its execute (ready on console). But now, I not understand the next step for execute....

@carletto
Copy link

carletto commented Feb 9, 2016

I have Solved!
I renamed the file electron.js in main.js and i 've modified the parameters inside package.json

After cancel electron.js from directory.

package.json:
{
"name": "screencat",
"version": "4.2.0",
"description": "webrtc screensharing with shared mouse and keyboard",
"main": "main.js",
"scripts": {
"start": "electron main.js",
....

Now screencat starts! But I have others errors on deprecated function and on robot.js but this is another story ;-)

@fritx
Copy link

fritx commented Mar 24, 2016

yeah, same here..
in windows, electron electron.js would just open up the file electron.js
need to either rename the electron.js or c:\path\to\electron electron.js

@mattwkelly
Copy link

mattwkelly commented Oct 7, 2016

Thanks for posting the fixes. Confirming these work, but now when I run 'npm start' it's stuck-- it just says 'ready' in console.

Edit: In my tiredness, I didn't notice screencat is actually running. :) So this issue is resolved for me.

@zhanls
Copy link

zhanls commented Jun 11, 2019

Thanks for posting the fixes again. It works in my pc at least.
Though you just have to find the "hidden" the black cat in the windows 10 task bar:
1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants