Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 10060
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Mark Fenner <mfenner@gmail.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 10060 depends on: Show dependency tree
Bug 10060 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2002-11-01 13:03 0000
Unfortunately I don't know much about the architecture of 
python/sip/pyqt/pykde, but as per: 
 
*begin quote* 
Sounds like it. The sip files (portable) are used to 
generate the cpp/h files (platform specific), and 
then the cpp files are compiled to build the actual 
bindings libs. PyQt no longer needs the sip files 
when that's done, but any other PyQt based bindings 
(PyKDE and I presume PyQwt) need the PyQt sip files 
kind of like the way cpp files need h files from a 
lib you're linking to - they're needed so that all 
symbols can be resolved when sip is generating the 
cpp code for the next PyQt based module. 
*end quote* 
 
[I'm not sure how to reference a newsgroup discussion.  You can  
find the thread on comp.lang.python with subject "PyQwt" started by 
me (Mark) on Oct. 31.  Jim responded with the above ... it hasn't made  
its way into groups.google yet] 
 
I presume that the PyQt ebuild should install the *.sip files to some 
common location.  Perhaps /usr/share/sip/*.sip?  I can look into  
modifying the ebuild to do this, but I wanted confirmation that this 
is necessary. 
 
Regards, 
Mark

------- Comment #1 From Dan Armak (RETIRED) 2003-01-30 09:18:06 0000 -------
I agree that this needs to be done. 
However I do not know, and have been unable to find, the default/standard/recommended 
location to place the sip files. I checked the suse and mdk packages, and theyb don't sintall the 
sip files at all. Why do you suggest /usr/share/sip, is it a default somewhere? Where does 
pykde expect to find them? 

------- Comment #2 From Mark Fenner 2003-01-30 16:04:09 0000 -------
PyQwt requires you to set a variable during the compile process that points to  
qt.sip and friends.  I think PyKDE does some searching.  I'm not sure where it
expects 
them.  Maybe PyKDE includes its own copies?  The source I downloaded to
investigate 
this is a bit old now ... it may be out of date. 

I decided on /usr/share/sip based on a whim.  It doesn't seem to me it should
go in an 
*include* directory, since those are for C/C++ include files.  I also hate
non-libraries in 
any lib directory (although it is allowed by the hierarchy standard). 

Regards, 
Mark 

------- Comment #3 From Dan Armak (RETIRED) 2003-02-17 12:40:14 0000 -------
OK, I'm back on this... I found the (official?) redhat rpm (the one that's on
the pyqt site, not on 
the redhat site) and it puts pyqt's .sip files in /usr/share/sip/qt. Good
enough; I've made the 
ebuild (a new revision) put them there. 

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug