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
Add 'configure', 'build' and 'clean' hooks. #9
Comments
…, and 'build' commands. Part of #9.
second this request... really useful if you need custom libraries outside your normal directories, etc. |
I don't really think this is needed anymore. It's possible to hook into "configure" and "build" using just |
Gotcha, yes found this out recently. thanks! |
This would still be useful since gyp's 'actions' are finicky on Windows builds |
I think we should re-open this issue. Having a reliable way of implementing cross-platform pre/post build steps would be very helpful for more complex native module builds. Building libxmljs fully from scratch requires several stages that could be automated with proper hooks. We currently package large source files that could be generated on the fly as-needed, while keeping our NPM footprint as small as possible. GYP-based solutions aren't working, not to mention GYP itself is really showing it's age. |
For more complex module build systems, like
node-ffi
, where the bundled libffi also needs to be configured and built, there should be hooks into the build steps for modules. The hooks should be node JavaScript files and will need to manually take care of platform differences in their scripts.I'm thinking that these should be hard-coded script names (i.e.
gyp-configure.js
,gyp-build.js
, andgyp-clean.js
) which would be run if they exist, before the rest of the step.The text was updated successfully, but these errors were encountered: