[PySide] Building PySide 1.2.1 Windows

Fri Jan 10 02:03:57 CET 2014

It would be great if it could be detected.  This was tricky to solve in
that no information was given about what the problem was.  Only when
running shiboken by hand as per Sean's suggestion did I start to have a
trail to follow.

Thanks everyone!

-tony

On Thu, Jan 9, 2014 at 7:25 PM, Roman Lacko <backup.rlacko at gmail.com> wrote:

> 2014/1/10 anatoly techtonik <techtonik at gmail.com>
>
>> Should a build system be modified to detect this case and warn about it?
>>
>
> yes build system could detect if there are more qmake programs in path and
> warn user, but i think the problem is that shiboken process is started vith
> bad environment. I will do some tests...
>
> roman
>
>
>>
>> --
>> anatoly t.
>>
>>
>> On Thu, Jan 9, 2014 at 9:28 PM, Sean Fisk <sean at seanfisk.com> wrote:
>>
>>> Ah, nice! That’s what I was going to suggest.
>>>
>>> The error you received when trying to run shiboken was reported by
>>> Windows’ dynamic library loader. If you need to debug more of these issues
>>> in the future, I highly recommend Dependency Walker<http://www.dependencywalker.com/>,
>>> which is the functional equivalent of ldd on GNU/Linux and otool -L on
>>> Mac OS X.
>>>
>>> Anyway, I’m glad you got it figured out. Always happy to help :)
>>>
>>>
>>> --
>>> Sean Fisk
>>>
>>>
>>> On Thu, Jan 9, 2014 at 1:22 PM, Tony Barbieri <greatrgb at gmail.com>wrote:
>>>
>>>> Thanks to your help I was able to find the issue.  There was another Qt
>>>> distribution first in my path hidden inside another application.
>>>>
>>>> Sorry for the noise and again, I really appreciate your help Sean!
>>>>
>>>> -tony
>>>>
>>>>
>>>> On Thu, Jan 9, 2014 at 12:37 PM, Tony Barbieri <greatrgb at gmail.com>wrote:
>>>>
>>>>> Hi Sean,
>>>>>
>>>>> When running shiboken.exe I receive the error shown in the attached
>>>>> image.
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> Unfortunately I can't use the provided binaries because I'm trying to
>>>>> target an older Qt release, 4.7.1, due to some restrictions with software
>>>>> we use with embedded Qt.
>>>>>
>>>>> I really appreciate your help with this.
>>>>>
>>>>> -tony
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Jan 9, 2014 at 12:07 PM, Sean Fisk <sean at seanfisk.com> wrote:
>>>>>
>>>>>> Hi Tony,
>>>>>>
>>>>>> It looks like the Shiboken executable was successfully built, and the
>>>>>> build errored out when trying to run it. Can you run
>>>>>> W:\PySide\1.2.1\pyside_build\py2.7-qt4.7.1-64bit-release\shiboken\generator\shiboken.EXEto try to see if it’s even a correct build? (e.g., do
>>>>>> --help and --version at least work). This will give us more of an
>>>>>> idea of what return code '0xc0000139' means.
>>>>>>
>>>>>> I notice your source directory is on a different drive. While there’s
>>>>>> a 99% chance this *isn’t* the problem, I just want to warn you that
>>>>>> one time I had a problem with files being on a different drive, and it had
>>>>>> to do with Visual Studio.
>>>>>>
>>>>>> Just curious — is there some reason that you aren’t able to use the
>>>>>> binaries <http://qt-project.org/wiki/PySide_Binaries_Windows>? Of
>>>>>> course, this doesn’t solve your problem but if you just want to use PySide
>>>>>> they should work. Probably whoever compiled those binaries could help you a
>>>>>> bit more.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sean Fisk
>>>>>>
>>>>>>
>>>>>> On Thu, Jan 9, 2014 at 11:26 AM, Tony Barbieri <greatrgb at gmail.com>wrote:
>>>>>>
>>>>>>> Thanks Sean!
>>>>>>>
>>>>>>> Attached is the complete log.  Thanks again for the help.
>>>>>>>
>>>>>>> -tony
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jan 9, 2014 at 11:16 AM, Sean Fisk <sean at seanfisk.com>wrote:
>>>>>>>
>>>>>>>> You should be able to use this from Windows Command Prompt, Visual
>>>>>>>> Studio Command Prompt, or PowerShell:
>>>>>>>>
>>>>>>>> $ compile_command > compile.log 2>&1
>>>>>>>>
>>>>>>>> Or if you’re in PowerShell (or Bash, for that matter), you can send
>>>>>>>> it to a file and view it at the same time:
>>>>>>>>
>>>>>>>> $ compile_command 2>&1 | tee compile.log
>>>>>>>>
>>>>>>>> That’s how I usually do it. Let me know if that works.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sean Fisk
>>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Jan 9, 2014 at 11:05 AM, Tony Barbieri <greatrgb at gmail.com>wrote:
>>>>>>>>
>>>>>>>>> Is the log saved out somewhere?  That is all that's printed to the
>>>>>>>>> output window.  Can I make it more verbose somehow?
>>>>>>>>>
>>>>>>>>> Thanks much!
>>>>>>>>>
>>>>>>>>> -tony
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thu, Jan 9, 2014 at 11:04 AM, Sean Fisk <sean at seanfisk.com>wrote:
>>>>>>>>>
>>>>>>>>>> Hi Tony,
>>>>>>>>>>
>>>>>>>>>> Yikes, that's not a very helpful error message, is it? I've built
>>>>>>>>>> Shiboken a number of times, but never on Windows. Can you post the full log
>>>>>>>>>> so we have a little more context? As an attachment would probably be
>>>>>>>>>> preferable.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sean Fisk
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thu, Jan 9, 2014 at 10:55 AM, Tony Barbieri <
>>>>>>>>>> greatrgb at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hello!
>>>>>>>>>>>
>>>>>>>>>>> I am trying to build PySide 1.2.1 against Qt 4.7.1 on Windows
>>>>>>>>>>> using VS 2010.
>>>>>>>>>>>
>>>>>>>>>>> I seem to continually hit an error when running generator on
>>>>>>>>>>> shiboken.  Not much info is given but the following is output:
>>>>>>>>>>>
>>>>>>>>>>> [ 98%] Running generator for 'shiboken'...
>>>>>>>>>>> NMAKE : fatal error U1077:
>>>>>>>>>>> 'W:\PySide\1.2.1\pyside_build\py2.7-qt4.7.1-64bit-release\shiboken\generator\shiboken.EXE'
>>>>>>>>>>> : return code '0xc0000139'
>>>>>>>>>>> Stop.
>>>>>>>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft
>>>>>>>>>>> Visual Studio 10.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
>>>>>>>>>>> Stop.
>>>>>>>>>>> NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft
>>>>>>>>>>> Visual Studio 10.0\VC\BIN\amd64\nmake.exe"' : return code '0x2'
>>>>>>>>>>> Stop.
>>>>>>>>>>> error: Error compiling shiboken
>>>>>>>>>>>
>>>>>>>>>>> Any help would much appreciated!
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> -tony
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> PySide mailing list
>>>>>>>>>>> PySide at qt-project.org
>>>>>>>>>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> -tony
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> -tony
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -tony
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> -tony
>>>>
>>>
>>>
>>> _______________________________________________
>>> PySide mailing list
>>> PySide at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/pyside
>>>
>>>
>>
>> _______________________________________________
>> PySide mailing list
>> PySide at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/pyside
>>
>>
>
> _______________________________________________
> PySide mailing list
> PySide at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
>
>

-- 
-tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20140109/1868962e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: shiboken-error.jpg
Type: image/jpeg
Size: 83332 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20140109/1868962e/attachment.jpg>