Replies: 2 comments 1 reply
-
I guess that’s because you are building it using the docker container instead of “natively” with nix. That means that each time you build it the build cache is empty. Ideally you’d have nix installed locally but I understand that might not be an option for casual contributors. I have an idea to improve this so I will test it out and push it shortly so you can test it.
That means you had changed in your github repo that weren’t added with |
Beta Was this translation helpful? Give feedback.
-
|
Would you mind testing this PR? The idea is to pre-cache in the docker container the vips build and all of the build dependencies (which shouldn't change often) so the build time is exclusively related to the changes done to the go code. The builder image becomes quite big but that's to be expected as the toolkit and dependencies needed to build vips is quite big. I also added a make target to get access to the build environment so you can run commands there by hand. |
Beta Was this translation helpful? Give feedback.
-
|
@dbarrosop |
Beta Was this translation helpful? Give feedback.
-
I am on an intel mac, and the fact that i don't have to deal with "pkg-config --cflags -- vips" is great...
But the nix package is taking ages each time . About 5 to 10 minutes.. The cache is always dirty also.
What about a docker image with golang and libvips all in one.
https://github.com/cshum/imagor has some merit...
It has s3 support: https://github.com/cshum/imagor#aws-s3, but not sure about auth and presigned URLS, etc
Beta Was this translation helpful? Give feedback.
All reactions