I need to compile poco with MinGW so I can use it in Qt Creator but cannot figure out how to, I've managed to compile poco in Visual Studio but I cannot use those libraries in Qt Creator.
相关问题
- QML: Cannot read property 'xxx' of undefin
- QTextEdit.find() doesn't work in Python
- QT Layouts, how to make widgets in horizontal layo
- QT GUI freezes even though Im running in separate
- QGraphicsView / QGraphicsScene size matching
相关文章
- ubuntu20.4中c#通过c++库调用python脚本
- Qt槽函数自动执行多遍
- Is there a non-java, cross platform way to launch
- How to get a settings storage path in a cross-plat
- Why doesn't valgrind detect a memory leak in m
- QTreeView remove decoration/expand button for all
- qt界面拥挤
- how do I correctly return values from pyqt to Java
Building POCO with MinGW should not be a big deal, it's been done in the past but core developers have no incentive (not our "itch") and none of the folks complaining steps up to own and maintain MinGW build; we'd more than welcome someone taking that role. Anyone interested can contact me.
There maybe a error as follow:
we can resolve the problem by change line in file "build\rules\global"
to
With this enviroment:
This is how I configure and compile Poco for MinGW and Windows 7:
Apply the next path to avoid copysign error.(From https://github.com/pocoproject/poco/issues/57).
In the file C:\poco-1.4.6\Foundation\include\Poco\FPEnvironment_DUMMY.h
Delete the string std:: in this method:
And here too:
Modify MinGW configuration at C:\poco-1.4.6\build\config\MinGW. (From http://cidebycide.blogspot.com.es/2012/06/building-poco-c-witn-mingw.html)
You should delete the -mno-cygwin string in line:
and
If you don't need to use cryptography and SSL, you should remove the options -lssl, and -lcrypto at SYSLIBS line.
Compile Poco without demos, SSL, cryptography and ODBC support:
Good luck!
Complementing Cesar's answer (here, instead of adding a comment, for formatting purposes), you need something like this on your .pro file:
E.g., in my case, I would have this (for debug builds):
You can then refine this a bit, by creating settings for both debug and release builds:
Hope this helps.