Log file Viewer

[15:02:36] <Kronuz> good morning

[15:02:58] <Kronuz> hey, how does Pillow build the wheels for the package?

[15:03:09] <Kronuz> is there an online service that does that?

[15:35:57] <wiredfool> Kronuz: we've got a repo that does it on travis: https://github.com/python-pillow/pillow-wheels

[15:36:29] <Kronuz> wiredfool, yes, I saw that, you use Travis CI for building the OS X wheels

[15:36:44] <Kronuz> and the other ones (including windows) you build them manually, right?

[15:39:19] <wiredfool> windows builds are done by cgohlke. I've tried to setup automated builds for those but haven't gotten everythign right

[15:44:03] <Kronuz> I'm working in the CodeIntel package, and since it has a bunch of binaries (actually just four), I want those to be in wheels

[15:44:46] <Kronuz> the tricky part is also that one of the extensions need pcre and libstdc++

[15:45:06] <Kronuz> (which most likely I think I want to have statically linked)

[15:47:55] <wiredfool> linking with the current packaging tools is...

[15:48:30] <wiredfool> well. if it all works the way you want out f the box, great, otherwise it's a pain.

[15:49:08] <wiredfool> pretty sure that we're statically linking on win, dynamic on linux.

[15:49:36] <wiredfool> but there's a low level recurring hteme of people wanting to use their own libraries, rather than whatever we find.

[16:21:56] <Kronuz> wiredfool, it's always a mess, binaries...

[16:23:18] <Kronuz> on linux there's the problem that things run in one linux but not the other (for some reason) ...ABI, API, architecture, compilation mode, blah, blah...

[16:23:53] <Kronuz> I have had the most problems with the one that needs libstdc++

[16:25:16] <Kronuz> which I once read in linux should be statically linked for better binary compatibility (while still dynamically linking glibc)