On 03/21/2012 10:08 PM, Darrell Anderson wrote:
>>   I am working to build sip4-tqt and I'm running into
>> problems telling python
>> configure.py where to find the include files. I patched
>> sipgen/sip.h to #include
>> <tqt/tqt.h> which allow it to find tqt.h, but then it
>> failed to find the next
>> include:
>>
>> /usr/include/tqt/tqt.h:54:23: fatal error: ntqglobal.h: No
>> such file or directory
>>
>>   which is in
>>
>> /opt/tqt3/include/ntqglobal.h
>>
> 
> 
<snip>
> 
> 
> Notice I keep the help parameters in the script for easier future reference. I have done likewise for the other python related build scripts.
> 
> In Slackware, sip is installed as a stock package. Therefore I have to name my final Trinity sip4-tqt package to sip in order to get the package tools to update the existing sip package rather than just install the package (because then I'd have two conflicting sip packages installed).
> 
> I am installing sip4-tqt, python-tqt, python-trinity, pytdeextensions, and libtqt-perl to /usr rather than /opt/trinity because most of the files get installed in python/perl subdirectories anyway. Further, the stock Slackware sip package is installed in /usr and any other stock package depending on that location needs to find the Trinity version in the same location.
> 
> Darrell
> 

Thanks Darrell,

  sip4-tqt built. Arch also has sip in /usr/bin. Are you simply replacing the
slack sip with the sip4-tqt? Sounds like it. In that case, the Arch sip is
python3 based while sip4-tqt is python2 based. What kind of issues would
replacing it cause? (shouldn't matter, but I thought I would ask if you know)

  I can build sip4-tqt as sip or I can just set the conflicts and replaces
flags. I'll mess with it.

-- 
David C. Rankin, J.D.,P.E.