Re: Packaging FreeCAD

[John Soo <jsoo1@asu.edu>]

[-- Attachment #1: Type: text/plain, Size: 3970 bytes --]

Hi all,

I have some more news on FreeCAD.

 - I responded to two tickets in two coin repos that will be needed to update coin and Pivy:
  + ticket on soqt: https://bitbucket.org/Coin3D/soqt/issues/6/wrong-path-for-soqt_library_dirs
  + ticket on coin: https://bitbucket.org/Coin3D/coin/issues/175/coin-build-errors-with-linux-and-osx
 - FreeCAD is compiling, but there is an install-phase error involving the Salome library SMESH. FreeCAD bundles smesh and a couple other libraries in the source. I inquired on their forum and have a few steps I can try this week.
  + I would like to use FreeCAD’s versions if possible. What is our stance on using bundled libraries?
  + Advantages of using the SMESH bundled with FreeCAD include not needing to package the various Salome libraries needed to compile SMESH.  Some of those transitive dependencies include omniORB and opencascade itself. I spent a lot of this weekend trying to package SMESH and I came to realize that if we were to package it, we would need to also package opencascade-occt and we would not be able to use oce which we have already.

Thanks for your patience on this. As always, my work is available on master at https://github.com/jsoo1/guix-channel. Thanks for your patience on this one. It has been a long and instructive exercise. I will be on vacation the coming two weeks, so I won’t be able to work on it. I know it’s already been months, now and I hope it can be done in maybe two more. Hopefully before the next release of FreeCAD.

- John

>> On Mar 9, 2019, at 11:25 PM, Efraim Flashner <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 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 so far
>> and the error: https://paste.debian.net/1072533. Any help would 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.  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   <efraim@flashner.co.il>   אפרים פלשנר
> GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
> Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: Type: text/html, Size: 9438 bytes --]