@estebanlm, Does scripts/installCygwin.bat get run each CI build? My PR will include adding installation of the "patch" package to this script. — |
In reply to this post by David T Lewis
yes it should — |
In reply to this post by David T Lewis
To summarise our Discord chat, — |
In reply to this post by David T Lewis
Sorry, I didn't test run installCygwin.bat and appveyor barfed the PR. — |
In reply to this post by David T Lewis
This has been merged in — |
In reply to this post by David T Lewis
Closed #319. — |
In reply to this post by David T Lewis
Unfortunately, after all this hard and appreciated work, we now have another CI problem: the build times out... https://ci.appveyor.com/project/OpenSmalltalk/vm/builds/21318435/job/b3npekwh7wnoa4jo/messages
We cannot re-build every library we need by ourself, it does not scale... — |
In reply to this post by David T Lewis
Maybe we may ask: https://help.appveyor.com/discussions/problems/16983-hitting-60min-build-timeout — |
In reply to this post by David T Lewis
I think something else must have gone wrong. I tested caching-disabled here...
I do believe there would be value in that, particularly to speed up building locally for the first time. — |
In reply to this post by David T Lewis
well, it should not be the build of freetype who adds so much time (and yes, time to build was ~30-40 minutes last time I checked). — |
In reply to this post by David T Lewis
On Wed, 2 Jan 2019 at 20:14, Esteban Lorenzano <[hidden email]> wrote: > well, it should not be the build of freetype who adds so much time (and > yes, time to build was ~30-40 minutes last time I checked). > If needed, for different reasons, in the Pharo win64 build I started to > put third party libraries in a repository and download them from there... > maybe we can do the same for the 32bit build? > I was curious about the different arrangement for win64. Could you point to that repo? cheers -ben — |
In reply to this post by David T Lewis
is in the makefiles for pharo.cog.spur :) http://files.pharo.org/vm/pharo-spur64/win/third-party/ — |
On Wed, 2 Jan 2019 at 20:41, Esteban Lorenzano <[hidden email]> wrote:
Cool. But what is the heritage of those files? Is there a version controlled makefile that built them? |
In reply to this post by David T Lewis
That's the advantage of using cygwin pre-built libraries: they are compiled for us and security patches are applied sooner than if we manage them by ourself. And that's the drawback: we have no control on exact version (apart major version), and library can change from one build to another. But it's the same if you use pre-built libraries from macosx and linux (libc, libm, etc...). We have to trust... — |
Free forum by Nabble | Edit this page |