Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
getting PySide to work
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
mike  
View profile  
 More options May 17 2011, 2:22 am
From: mike <mj...@nephosity.com>
Date: Mon, 16 May 2011 23:22:03 -0700 (PDT)
Local: Tues, May 17 2011 2:22 am
Subject: getting PySide to work
Hi all,

The following patch (everything between the starred lines) is how I
got PySide working with PyInstaller on my Mac.  My version of PySide
is the binary distribution from the PySide website.  What I see is
that the PySide developers install the libraries into /usr/lib, which
is excluded by default by PyInstaller.  I agree that /usr/lib on the
Mac is probably/usually not installed into by 3rd party libraries, it
does so happen on occasion.  In this case, I don't know what the best
solution is (which may include asking PySide to change their install
location).  In any case, just wanted to share the results of my
findings.

******************************************
Index: PyInstaller/bindepend.py
===================================================================
--- PyInstaller/bindepend.py    (revision 1406)
+++ PyInstaller/bindepend.py    (working copy)
@@ -411,7 +411,11 @@
             candidatelib = npth
         else:
             candidatelib = lib
-        if (excludesRe.search(candidatelib) and (not includes or
+
+        if candidatelib.find('pyside') >= 0 or
candidatelib.find('shiboken') >= 0:
+            # do nothing
+            pass
+        elif (excludesRe.search(candidatelib) and (not includes or
             not includesRe.search(candidatelib))):
             if candidatelib.find('libpython') < 0 and \
                candidatelib.find('Python.framework') < 0:
@@ -462,7 +466,7 @@
         This implementation is for otool platforms"""
     # dyld searches these paths for framework libs
     # we ignore DYLD_FALLBACK_LIBRARY_PATH for now (man dyld)
-    fwpaths = ['/Library/Frameworks', '/Network/Library/Frameworks',
'/System/Library/Frameworks']
+    fwpaths = ['/Library/Frameworks', '/Network/Library/Frameworks',
'/System/Library/Frameworks', '/usr/lib']
     for p in reversed(os.environ.get('DYLD_FRAMEWORK_PATH',
'').split(':')):
         if p:
             fwpaths.insert(0, p)
******************************************


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Hartmut Goebel  
View profile  
 More options May 17 2011, 5:11 am
From: Hartmut Goebel <h.goe...@goebel-consult.de>
Date: Tue, 17 May 2011 11:11:36 +0200
Local: Tues, May 17 2011 5:11 am
Subject: Re: [PyInstaller] getting PySide to work

Am 17.05.2011 08:22, schrieb mike: candidatelib = lib

> -        if (excludesRe.search(candidatelib) and (not includes or
> +
> +        if candidatelib.find('pyside')>= 0 or
> candidatelib.find('shiboken')>= 0:
> +            # do nothing
> +            pass
> +        elif (excludesRe.search(candidatelib) and (not includes or
>               not includesRe.search(candidatelib))):
>               if candidatelib.find('libpython')<  0 and \
>                  candidatelib.find('Python.framework')<  0:

I do not like this "hack" for a single module/package. Isn't there
another solution?

--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP

Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de/blog

Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult mit Mitglied bei http://www.7-it.de

  smime.p7s
6K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
mike  
View profile  
 More options May 17 2011, 5:31 am
From: mike <mj...@nephosity.com>
Date: Tue, 17 May 2011 02:31:18 -0700 (PDT)
Local: Tues, May 17 2011 5:31 am
Subject: Re: getting PySide to work

> I do not like this "hack" for a single module/package. Isn't there
> another solution?

I agree that this hack is not desirable.

I simply thought to put it out there, as a topic of discussion, as
there are others waiting for PyInstaller to support PySide on Mac, but
to do so, we would need to change some assumptions that PyInstaller is
making about directories to include/exclude.  The good news is, unlike
PyQT, no hook files are necessary  :)

Cheers
Mike


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »