<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Phil Thompson wrote:
<blockquote cite="mid:eeb4689a355ac3e82ce349e6062d5300@localhost"
type="cite">
<pre wrap="">On Wed, 10 Mar 2010 16:49:13 -0500, Josh <a class="moz-txt-link-rfc2396E" href="mailto:jknox@irobot.com"><jknox@irobot.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
In my dev environment we build packages of Qt, PyQt, SIP, etc on a
"central" build machine. Developers use these packages as dependencies
for their projects on their own machines. The packages are always
installed in different locations than where they were originally built.
This leads to a problem where the plethora of paths specified in
pyqtconfig.sipconfig._config_stack all refer to the original build
machine. So, without some customization, its impossible to build
PyQt/SIP wrappers for our Qt C++ widgets.
My question is this: Is it correct to just pilfer through the elements
of pyqtconfig.sipconfig._config_stack and set things up for my system
(ie. string replace)?
</pre>
</blockquote>
<pre wrap=""><!---->
No - _config_stack is an internal implementation detail.
</pre>
<blockquote type="cite">
<pre wrap="">Doing that just feels wrong. Is there a better way
to go about this?
</pre>
</blockquote>
<pre wrap=""><!---->
No - what you are doing is simply unsupported.
Phil
</pre>
</blockquote>
OK, that's fine. I faced similar issues integrating Qt with our build
system. Just so I understand, are the official PyQt releases
built/installed into the exact same paths that are expected to be used
by end users? <br>
<br>
Thanks,<br>
<br>
Josh<br>
</body>
</html>