Hi all,
I've just got my Qt Creator plugin (aka PremakeProjectManager) opening projects on Windows. However, I had to make several strange things to achieve it:
1. I had to replace 'SetCurrentDirectory' with 'chdir' and 'GetCurrentDirectory' with 'getcwd'. Otherwise Premake was failing to use 'require' and 'include' with relative paths.
2. I had to comment out body of 'os_uuid' function. Qt Creator was segfaulting on it, however os.uuid() wasn't used in solution I'm currently testing.
All these issues happen only when I'm running Premake inside Qt Creator plugin - i.e. not in the main program module, and also not in the main thread. Stand alone premake4.exe works fine, Qt support also seems to work.
Share
BTW, after these changes plugin works (almost) fine and is capable of building Qt projects.
I've replaced dynamic loading of ole32.dll with conventional linking. Now Qt Creator does not crash anymore, and os.uuid() is working.
Note: I used VS 2008 Express for building (official Qt Creator and Qt SDK are build with VS 2008, so I have no choice).
I don't mind swapping out SetCurrentDirectory and GetCurrentDirectory, though that seems an odd error. Go ahead and submit a patch for that if you need it.
I don't remember why I thought I had to dynamically link ole32. Feel free to include that change in the patch as well.
Done: https://sourceforge.net/tracker/?group_id=71616&atid=531880
I've found that Windows implementation of os.matchfiles() is also broken in Qt Creator. Function FindFirstFile returns invalid handle, and reports "Error 123: The filename, directory name,or volume label syntax is incorrect".
Removing -DUNICODE added by QMake fixed the problem. Now I guess GetCurrentDirectory and SetCurrentDirectory failures were also due to Unicode.
Out of interest why would qmake have any effect on functions Premake uses?
I use it to build my plugin which includes complete source code of Premake (to simplify development I don't build them as separate libraries). I cannot use Premake instead of qmake to build my plugin because a) I need to build it with Visual Studio and my Qt support code supports only gmake action right now; b) Qt Creator uses qmake so there may be interoperability issues between build systems.