-
Notifications
You must be signed in to change notification settings - Fork 15
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
Chrome extension build fails on macOS #1
Comments
Hi, The Mac install requires a native messaging json file (like the one in the deb subdir), as well as a plist to install it. Unfortunately I lost most of the Mac packaging stuff in the conversion to open source, and I'm not sure of the best way to do Mac packaging/installers. |
Did anybody get it to run on macOS? I have the same issues. |
@nitramabuar I've built the extension on Ubuntu, and installed on Mac.
|
Hi, I've been building on Mac, although I had to set my max open files pretty high. If it fails due to maxfiles, just keep re-running and it'll get further. The EOF error is ok (I should probably not log it) - it means that nativeMessaging is getting called. |
@therealmik Thanks, but the problem is that the extension complains about the native part (it says the native part is not installed; I've tried different combinations of options, but no success; |
Building |
Hey
Running
bazel build chrome_ext
fails with this error:macOS 10.13.3
node 9.4.0 (npm 5.6.0)
bazel 0.9.0
FYI,
native_messaging
is built successfully.Update:
I built it on Ubuntu and installed the extension on Mac; Also, built the native messaging on Mac.
How should I configure the native package? (
detanglenm
binary).The extension complains that the native package is missing.
The text was updated successfully, but these errors were encountered: