Hi Guys (Catalin, Thomas) I have gone most of the same paths on Windows Vista + VS 2008, i am wondering why not join forces and make a trial all-merge of all of our modifications? however still have some issues building shiboken, but other libraries are building smoothly.
Please let me know if you are interested :) On Mon, Apr 12, 2010 at 10:37 PM, Thomas Berg <[email protected]> wrote: > Hi Catalin, > > On Sun, Apr 11, 2010 at 11:16 PM, Catalin Iacob <[email protected]> > wrote: > > At this point the 3 projects compile successfully! > > > > Shiboken generator plugin starts running for samplebinding and > > otherbinding but it gives lots of errors of the form > > c1xx : fatal error C1083: Cannot open source file: > > '.\sample\voidholder_wrapper.cpp': No such file or directory > > and afterwards crashes. > > > > Next I plan to look into the error messages and stack traces for the > > Shiboken crash (maybe related to the error messages?), go on to PySide > > and then come back and try to look at InnoSetup and the installers. > > I also did some experiments with Pyside on Windows, using SCons rather > than CMake. As a result I have not patched any of the CMake files. I > have done some other code fixes that were merged into shiboken and > pyside-shiboken today, which you may benefit from :-) > > - In addition to what you found, I fixed a link problem (dllimport > macros on inlined classes in shiboken) that only became visible when > building pyside-shiboken, this has been merged today > - I also submitted some MSVC fixes to pyside-shiboken > - I found the same missing include that you found, this has already been > merged. > > Some other findings: > - The problem with the missing "lib" prefix on windows can also be > fixed by modifying the build scripts, which is what I did in my SCons > build, so I have not submitted any patches for this. > - Like you, I found I had to add the Str::operator< to to make > shiboken/tests/libsample build. I have not submitted this to gitorious > yet, so you are welcome to do that > - I tracked down the shiboken crash to the vsnprintf call in > apiextractor/reporthandler.cpp:174, on my machine it only crashes in > release. If you have problems getting a stacktrace for the crash you > are seeing, try to comment out that call and see if it helps. I did > not have time to look more into this. > - all the apiextractor tests succeed when running them from the > debugger, but not when I run them from the shell, so maybe the fancy > reporthandler/stdout printing is causing the problems? > - I did some hacky changes just to get more of pyside-shiboken to > build: I had to add a missing #include <signalmanager.h> and replace > PyAPI_FUNC(void) with void to avoid duplicate dllexport macros in > generated code. The next problem I saw was the protected enum problem. > > I hope some of this helps you a bit further! I probably won't have > more time for it this week. > Thomas > _______________________________________________ > PySide mailing list > [email protected] > http://lists.openbossa.org/listinfo/pyside > -- Abdullah Abouzekry
_______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
