From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Soo Subject: Re: Packaging FreeCAD Date: Thu, 9 May 2019 13:50:22 +0000 Message-ID: References: <4071518a081f8bdf5b119dc774d9876ba8d5bd7b.camel@tourbillion-technology.com> <54206293-2C5D-4F2B-B213-888CAA38C93A@asu.edu> <8973E603-5C06-4E6E-837E-56C15E7599C0@asu.edu> <20190310072511.GB19750@macbook41> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000de554b058874bb61" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:53562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hOjRU-0008T4-Gj for guix-devel@gnu.org; Thu, 09 May 2019 09:50:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hOjRS-0003R1-RW for guix-devel@gnu.org; Thu, 09 May 2019 09:50:36 -0400 Received: from mail-vs1-xe2f.google.com ([2607:f8b0:4864:20::e2f]:35532) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hOjRS-0003QP-7q for guix-devel@gnu.org; Thu, 09 May 2019 09:50:34 -0400 Received: by mail-vs1-xe2f.google.com with SMTP id s4so1462458vsl.2 for ; Thu, 09 May 2019 06:50:33 -0700 (PDT) In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Efraim Flashner Cc: Guix-devel , Paul Garlick --000000000000de554b058874bb61 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello Guix, I have a few updates on progress packaging FreeCAD. - Thanks to the PySide developers, I have a rough draft of PySide2, PySide2-tools and Shiboken2 built. - FreeCAD gets through the build phase at version 0.18.1 (the current release) thanks to the PySide2 dependency. - Pivy, an optional dependency, still does not build yet, though I have been making some progress. - Coin has been undergoing a lot of development since I last defined the package and the updates will require extra work to package. - I'm confused by some licenses and I will probably ask for help clarifying them when I submit a patch, Thanks for your help and guidance, John On Tue, Mar 12, 2019 at 3:15 PM John Soo wrote: > Thanks Efraim! > > That helped a lot. I Switched to version 5.11.3 and swapped qt for qtbase > and some extra qt libraries and that moved me past the one blocker. Now I > am faced with another challenge. I packaged Shiboken 1 previously when I > did not realize freecad moved to pyside2; in that process I followed the > nix packaging strategy of building all the bundled libraries separately. = I > am now running into the same issues I had prior to splitting up Shiboken = 1 > while building pyside2. The python build system in pyside2 shells out to > cmake for most of the build process. That means it does not use > cmake-build-system. Does pyside2 need to be split into parts now? It is > more challenging for pyside2 that Shiboken 1 because the sources for all > the libraries are shipped together. Here's the source, for reference: > https://code.qt.io/cgit/pyside/pyside-setup.git/ > > Thank you all, > > John > > On Sun, Mar 10, 2019 at 7:25 AM Efraim Flashner > wrote: > >> On Sun, Mar 10, 2019 at 02:14:15AM +0000, John Soo wrote: >> > Hi guix, >> > >> > Just a quick update. I have little to report on freecad. I am still >> stuck >> > packaging pyside2. I have looked over the debian packaging rules but I >> am >> > unfamiliar with their packaging process. I did some research and it >> looks >> > as though they are using the normal pybuild process with some >> alterations >> > to some paths afterward. The package completely fails to compile for = me >> > and I am no expert on python build tooling. Here's what I have tried s= o >> far >> > and the error: https://paste.debian.net/1072533. Any help would be ver= y >> > appreciated. >> > >> > Thanks, >> > >> > John >> > >> > On Fri, Feb 15, 2019 at 6:33 PM John Soo wrote: >> > >> > > Thanks so much Paul! This is really helpful! >> > > >> > > > On Feb 15, 2019, at 9:20 AM, Paul Garlick < >> > > pgarlick@tourbillion-technology.com> wrote: >> > > > >> > > > Hi John, >> > > > >> > > >> I have been getting a little stuck building the pyside2 >> dependencies >> > > > >> > > > There has been an effort to package pyside2 for Debian. This has >> been >> > > > completed in the last six months. >> > > > >> > > > A good place to look for information is >> > > > https://tracker.debian.org/pkg/pyside2 >> > > > >> > > > You can browse the source code and follow the links to the 'debian= ' >> > > > directory, which contains the files that govern the packaging >> process. >> > > > In general for Debian packages, the 'rules' file is worth reading >> and >> > > > the 'patches' directory has the changes to the upstream code. >> > > > >> > > > One element that could be important in Guix is an update of >> patchelf to >> > > > a recent commit (see 'update-patchelf.patch' in the patches >> directory). >> > > > >> > > > Best regards, >> > > > >> > > > Paul. >> > > > >> > > >> >> I haven't tried building it myself yet, but two things come to mind: >> Try using qtbase instead of qt, it has a much smaller footprint and will >> likely be requested when it's time to include the package in Guix. >> >> You're using version 5.12.1, and in Guix we have qt 5.11.3. It's likely >> the errors you're getting are because the version of Qt is different. >> >> -- >> Efraim Flashner =D7=90=D7=A4=D7=A8=D7=99=D7= =9D =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8 >> GPG key =3D A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 >> Confidentiality cannot be guaranteed on emails sent or received >> unencrypted >> > --000000000000de554b058874bb61 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello Guix,

I have a few upd= ates on progress packaging FreeCAD.

=C2=A0 - Thank= s to the PySide developers, I have a rough draft of PySide2, PySide2-tools = and Shiboken2 built.
=C2=A0 - FreeCAD gets through the build phas= e at version 0.18.1 (the current release) thanks to the PySide2 dependency.=
=C2=A0 - Pivy, an optional dependency, still does not build yet,= though I have been making some progress.
=C2=A0 - Coin has been = undergoing a lot of development since I last defined the package and the up= dates will require extra work to package.
=C2=A0 - I'm confus= ed by some licenses and I will probably ask for help clarifying them when I= submit a patch,

Thanks for your help and guid= ance,

John

On Tue, Mar 12, 2019 at 3:15 P= M John Soo <jsoo1@asu.edu> wrote= :
Thanks Efraim!

That helped a lot. I Switch= ed to version 5.11.3 and swapped qt for qtbase and some extra qt libraries = and that moved me past the one blocker. Now I am faced with another challen= ge. I packaged Shiboken 1 previously when I did not realize freecad moved t= o pyside2; in that process I followed the nix packaging strategy of buildin= g all the bundled libraries separately.=C2=A0 I am now running into the sam= e issues I had prior to splitting up Shiboken 1 while building pyside2. The= python build system in pyside2 shells out to cmake for most of the build p= rocess.=C2=A0 That means it does not use cmake-build-system. Does pyside2 n= eed to be split into parts now? It is more challenging for pyside2 that Shi= boken 1 because the sources for all the libraries are shipped together.=C2= =A0 Here's the source, for reference: https://code.qt.io/cgit/pysid= e/pyside-setup.git/

Thank you all,
<= div>
John

On Sun, Mar 10, 2019 at 7:25 AM Efraim Fla= shner <efraim= @flashner.co.il> wrote:
On Sun, Mar 10, 2019 at 02:14:15AM +0000, John Soo wrote: > Hi guix,
>
> Just a quick update. I have little to report on freecad. I am still st= uck
> packaging pyside2. I have looked over the debian packaging rules but I= am
> unfamiliar with their packaging process. I did some research and it lo= oks
> as though they are using the normal pybuild process with some alterati= ons
> to some paths afterward.=C2=A0 The package completely fails to compile= for me
> and I am no expert on python build tooling. Here's what I have tri= ed so far
> and the error: https://paste.debian.net/1072533. Any help w= ould be very
> appreciated.
>
> Thanks,
>
> John
>
> On Fri, Feb 15, 2019 at 6:33 PM John Soo <jsoo1@asu.edu> wrote:
>
> > Thanks so much Paul! This is really helpful!
> >
> > > On Feb 15, 2019, at 9:20 AM, Paul Garlick <
> > pgarlick@tourbillion-technology.com> wrote:
> > >
> > > Hi John,
> > >
> > >> I have been getting a little stuck building the pyside2 = dependencies
> > >
> > > There has been an effort to package pyside2 for Debian.=C2= =A0 This has been
> > > completed in the last six months.
> > >
> > > A good place to look for information is
> > > https://tracker.debian.org/pkg/pyside2
> > >
> > > You can browse the source code and follow the links to the &= #39;debian'
> > > directory, which contains the files that govern the packagin= g process.
> > > In general for Debian packages, the 'rules' file is = worth reading and
> > > the 'patches' directory has the changes to the upstr= eam code.
> > >
> > > One element that could be important in Guix is an update of = patchelf to
> > > a recent commit (see 'update-patchelf.patch' in the = patches directory).
> > >
> > > Best regards,
> > >
> > > Paul.
> > >
> >

I haven't tried building it myself yet, but two things come to mind: Try using qtbase instead of qt, it has a much smaller footprint and will likely be requested when it's time to include the package in Guix.

You're using version 5.12.1, and in Guix we have qt 5.11.3. It's li= kely
the errors you're getting are because the version of Qt is different.
--
Efraim Flashner=C2=A0 =C2=A0<efraim@flashner.co.il>=C2=A0 =C2=A0=D7=90=D7=A4=D7= =A8=D7=99=D7=9D =D7=A4=D7=9C=D7=A9=D7=A0=D7=A8
GPG key =3D A28B F40C 3E55 1372 662D=C2=A0 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted=
--000000000000de554b058874bb61--