Re: Contribute to OSX-specific features and bug fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Travis let’s you store build artifacts and other things on each build.
What’s nice is it will check for changes and store new archives if they’re
different, and allow you to check when you start.

I imagine you could start incrementally building deps and storing them,
then only build what’s needed later (or update deps as needed).

I do something sort of like this myself. But my implementation is not very
sophisticated.
On Thu, Mar 29, 2018 at 3:49 AM Kristian Rietveld <kris@xxxxxxxxxxxx> wrote:

>
> > On 28 Mar 2018, at 15:27, Carmelo DrRaw <aferrero1975@xxxxxxxxx> wrote:
> >
> >
> > I am using homebrew to install the dependencies, honestly I find it more
> practical than jhbuild.
> > When creating the bundle, the libraries installed via homebrew are
> included so that the bundle is self-consistent.
>
> I use jhbuild on the one hand because it was in place when I took over the
> work on the build and because I am relatively familiar with it. On the
> other hand, it gives us full control over all versions of the dependencies
> and patches to apply in an easy way (we simply use our own jhbuild
> moduleset with all details and maintain this in the GIMP git repository).
> We do incorporate a number of patches to third-party modules (glib, GTK+,
> and so not) that have not been accepted upstream and I foresee this will
> remain so in the future.
>
>
> > Travis provides MacOS build servers. The only issue is that the jobs are
> limited to 40 minutes, which are obviously not enough to install all
> dependencies.
> > The solution I found is to do an incremental install of the homebrew
> packages via Travis itself, and save the resulting homebrew tree as a tar
> package that is stored back on github.
> > For the final build, I simply fetch and extract the pre-packaged tar
> file, which provides me all the required dependencies.
>
> 40 minutes is probably not enough. Sending around tarballs seems a bit
> hacky to me. I have another possible option for a build server that I will
> try first.
>
>
> thanks,
>
> -kris.
>
> _______________________________________________
> gimp-developer-list mailing list
> List address:    gimp-developer-list@xxxxxxxxx
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
_______________________________________________
gimp-developer-list mailing list
List address:    gimp-developer-list@xxxxxxxxx
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list




[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux