<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div><span>Great work! These actually contain some of the issues I didn't post workarounds for, for example the searching for "smokegen" while the file is named "smokegen.exe"</span>. It's good you compensated for my laziness. :)</div><div>I hope they take the parts for "ARCHIVE DESTINATION and RUNTIME DESTINATION". They do work and I had prepared such for smokegen. It was not accepted, though, because its validity on non-Windows system was doubted even though I actually read about it on a Linux-related mailing list, and I didn't have the time to check that AS WELL. Now that you tested it on Linux both yours and mine should be admitted. Once this happens, I'll send a patch for all CMakeLists in assemlygen/assemblies/qyoto-*/native.<br></div><div><br></div><div style="font-family: times new roman, new york, times, serif;
font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Steven Boswell II <ulatekh@yahoo.com><br> <b><span style="font-weight: bold;">To:</span></b> "kde-bindings@kde.org" <kde-bindings@kde.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, December 6, 2011 5:22 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> [Kde-bindings] Patches to vastly improve building smokegen/smokeqt/qyoto on Windows<br> </font> <br>
<div id="yiv1283955091"><div><div style="color:#000;background-color:#fff;font-family:times new roman, new york, times, serif;font-size:12pt;"><div>A few days ago, I reported a massive number of weird build issues that I ran into while trying to compile smokegen, smokeqt, and qyoto for Windows. Most of them could be solved by someone that knows CMake. I finally learned about CMake over the weekend...it was a lot less nasty than I was expecting. I guess autoconf has traumatized me. :-)</div><div><br></div><div>Anyway, I found what I would consider to be proper solutions to the vast majority of the build problems I ran into! Enclosed is an archive with three patches, one for each project, against the latest state of the public git repositories. Here's what they do:</div><div><br></div><div>smokegen:</div><div>Adds CMAKE_EXECUTABLE_SUFFIX to the end of SMOKE_GEN_BIN and SMOKE_API_BIN, so that the installed SmokeConfig.cmake
will have proper
paths to the executables.</div><div>Put quotes around several references to path variables, so that spaces can appear in the installation path.</div><div>Added ARCHIVE DESTINATION and RUNTIME DESTINATION to the install line of cppparser. (No apparent effect under Linux.)</div><div><br></div><div>smokeqt:</div><div>Put quotes around the reference to SMOKE_CMAKE_MODULE_DIR, so that spaces can appear in the installation path.</div><div><br></div><div>qyoto:</div><div>Modified paths to C# sources under Windows, changing forward-slashes to backward-slashes. (Apparently, Microsoft's C# compiler can't handle forward slashes.)</div><div>When looking for the C# compiler, if the environment variable CSC refers to the 2.0 compiler, don't use it. (The Qyoto C# files use .NET 3.0 features.)</div><div>If CMakeDetermineCSharpCompiler.cmake has to look for a Microsoft compiler, use the 3.5 version.</div><div>Don't compile QtDBus-related items unless
the related library was found (i.e. only if SMOKE_QTDBUS_LIBRARY is defined).</div><div>Added ARCHIVE DESTINATION to the install line of qtscript-sharp, qttest-sharp, qtuitools-sharp, and qtwebkit-sharp.</div><div>Changed the external definition of Qyoto_handlers[] in src/qyoto.cpp from Q_DECL_IMPORT to Q_DECL_EXPORT, to match the way it's declared elsewhere.</div><div>Define QDESIGNER_UILIB_LIBRARY when compiling uics for Win32, to get rid of a ton of linker errors.</div><div><br></div><div>I know that no one has time to help Dimitar and I port Qyoto to Windows, but at the very least, could you look over these changes and consider them for inclusion in the public git repository? I'll send a push request if that would make things easier for you.</div><div><br></div><div>Steven Boswell</div><div><br></div></div></div></div><br>_______________________________________________<br>Kde-bindings mailing list<br><a ymailto="mailto:Kde-bindings@kde.org"
href="mailto:Kde-bindings@kde.org">Kde-bindings@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/kde-bindings" target="_blank">https://mail.kde.org/mailman/listinfo/kde-bindings</a><br><br><br> </div> </div> </div></body></html>