Hi Ricardo, Thanks. I've been hacking in my channel and master usually has my current work: https://github.com/jsoo1/guix-channel/blob/master/python-pyside.scm - current commit is 59f6da3. <https://github.com/jsoo1/guix-channel/commit/59f6da338ceab793be5c81407e46cd03424b8ae7> Aside - I would like to patch most of the working and compatible packages in the channel back into guix, but freecad has been taking all my guix hacking time. I've attached the build log since there are some errors building both the apiextractor package and the shiboken library. Note that python-pyside.scm includes work on version 1 of the Shiboken library. That build seemed ok but freecad is moving to pyside2. I followed nix's strategy of building the packages separately and using cmake-build-system instead of python ( https://github.com/NixOS/nixpkgs/blob/2d656a9729739e8ca5486058a76669d0ea4442df/pkgs/development/python-modules/pyside/shiboken.nix#L33) for version 1. Pyside 2 is bundled into a single repository so I am not sure I can do the same thing for it. Thanks again!
- John On Thu, Mar 28, 2019 at 10:46 AM Ricardo Wurmus <rek...@elephly.net> wrote: > [- pyside] > > Hi John, > > > I’ve tried using the provided python build process but I get several > > build errors, let alone runtime issues. Would anyone be able to point > > me in a direction to patch pyside for such a packaging system? > > Currently I’m stuck building Shiboken. I’d particularly like guidance > > on how to setup cmake to build it correctly (mostly the ability to > > provide our particular flags and variables). Any help would be greatly > > appreciated. > > Could you show us the package definition you have so far? Can you also > show us what errors you get? > > -- > Ricardo > >
p52jx2x4c7s2ybx4mj4gv8m97mnaxr-python-pyside-2-v5.11.3-1.4018787.drv.bz2
Description: Binary data
