-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Compilation error on Travis #378
Comments
|
@lovell Yes, I understand. My concern that I cannot ask users to setup compiler on CI. It is not acceptable. In the readme of this project I see that "Most Windows (x64), Linux and ARMv6+ systems do not require the installation of any external runtime dependencies.", so, my question is why no precompiled binaries for Travis server (Ubuntu 12.04.5 LTS). |
A pre-compiled copy of libvips and its dependencies are provided so people don't have to compile and install them globally. For example, this allows people to use the fast, sudo-less Travis container environment. I notice you're using Electron. See also #313 |
Sorry for misunderstanding — A lot of people use it and I cannot ask everyone to install C++11 compiler. My previous approach was to use gm. And it seems I have to move back to it. Thanks for quick response. |
I guess in this case it's a trade off between failing at run-time because GraphicsMagick is not globally installed vs failing at install-time because the compiler is not suitable for Node v4+ native modules. If image processing is an optional feature, you could use npm's Some native modules use |
Closing this question as it looks like |
In the #42 I see that should be a precompiled version for Linux.
So, I don't understand why error https://travis-ci.org/loopline-systems/electron-builder/jobs/116341251#L268 occurred.
The text was updated successfully, but these errors were encountered: