unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Soo <jsoo1@asu.edu>
To: "Cristián Maureira-Fredes" <Cristian.Maureira-Fredes@qt.io>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	"pyside@qt-project.org" <pyside@qt-project.org>
Subject: Re: Packaging for guix
Date: Sat, 27 Apr 2019 15:31:47 +0000	[thread overview]
Message-ID: <CAKf5CqWnzLh8QJqba4BuPRvroqn=kALszVmuuENPOC93bR8Yew@mail.gmail.com> (raw)
In-Reply-To: <CAKf5CqXKf3+NyRhvKPJgcfffJqJvJevEpDv5EN82xFGJmQHZDw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2765 bytes --]

Hi Cristián and Ricardo,

A quick update: Shiboken2 builds! Thanks for your guidance!  I may have
more questions when building freecad itself, but this was very helpful.
Thanks again!

- John

On Fri, Apr 19, 2019 at 1:06 PM John Soo <jsoo1@asu.edu> wrote:

> Hi Cristián,
>
> Thank you! I have been following the cmake path and it seems to be working
> better than before. If I find more issues, I will ask.  Thanks again!
>
> - John
>
> On Wed, Apr 10, 2019 at 9:47 AM Cristián Maureira-Fredes <
> Cristian.Maureira-Fredes@qt.io> wrote:
>
>> Hello John,
>>
>> I'm not familiar with guix, but if the CMake approach doesn't work [1]
>> and the setuptools also doesn't work [2],
>> maybe you can share some of the logs related the build errors
>> so we can see how what's precisely the issue.
>>
>> Cheers
>>
>> [1]
>> https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/shiboken2
>> [2] https://wiki.qt.io/Qt_for_Python/GettingStarted/X11
>> ________________________________________
>> From: PySide <pyside-bounces@qt-project.org> on behalf of John Soo <
>> jsoo1@asu.edu>
>> Sent: Thursday, March 28, 2019 06:21
>> To: pyside@qt-project.org
>> Cc: guix-devel@gnu.org
>> Subject: [PySide] Packaging for guix
>>
>> Hello pyside maintainers,
>>
>> Hope you are all well.  I am looking to package freecad for the guix
>> package manager for which pyside is a dependency. I’m having some trouble
>> packaging pyside as the build and environment for guix (like nix) are quite
>> different from a Debian style system. There a quite a few differences:
>>
>>  -  the prefix for installation directories is in a unique directory
>> specific to the package
>>  - cmake and python require many particular environment variables and
>> flags
>> - library and linking paths are very different and often source shebangs
>> and linking paths need to be patched to point to the correct paths
>>  - the build process happens in an isolated build environment apart from
>> any system directories
>>  - probably more that I haven’t come across yet
>>
>> 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.
>>
>> Thank you,
>>
>> John
>> _______________________________________________
>> PySide mailing list
>> PySide@qt-project.org
>> https://lists.qt-project.org/listinfo/pyside
>>
>

[-- Attachment #1.2: Type: text/html, Size: 4070 bytes --]

[-- Attachment #2: Type: text/plain, Size: 135 bytes --]

_______________________________________________
PySide mailing list
PySide@qt-project.org
https://lists.qt-project.org/listinfo/pyside

  reply	other threads:[~2019-04-27 15:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28  5:21 Packaging for guix John Soo
2019-03-28 10:45 ` Ricardo Wurmus
2019-03-28 13:46   ` John Soo
2019-04-10  9:47 ` Cristián Maureira-Fredes
2019-04-19 13:06   ` John Soo
2019-04-27 15:31     ` John Soo [this message]
2019-05-03 16:43       ` John Soo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKf5CqWnzLh8QJqba4BuPRvroqn=kALszVmuuENPOC93bR8Yew@mail.gmail.com' \
    --to=jsoo1@asu.edu \
    --cc=Cristian.Maureira-Fredes@qt.io \
    --cc=guix-devel@gnu.org \
    --cc=pyside@qt-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).