New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems during compilation of Poco on Windows with MinGW and Cywgin #1071
Comments
@Alicech |
When I install Cygwin it shows me a list of libs that Cygwin could install during it's installation and Poco was one of those, I simply selected Poco and click next. And I read in a stackoverflow that Poco could compile with MinGW here it's the link I follow to install with MinGW: http://stackoverflow.com/questions/14637797/compile-poco-with-mingw-on-windows |
It will compile with MinGW, people come from time to time, contribute patches and disappear. But that build is not actively maintained |
ok, so what do you suggest I do ?? How can I compile Poco to make sure it works on windows ?? |
There are many ways, the simplest one being (1) opening each Visual Studio individual solution and building it (VS can be obtained free these days, I hear). Then, there are (2) batch and (3) PowerShell (still somewhat experimental) build scripts as well as (4) CMake support. Note that all of these build using Visual Studio on windows, currently we support it back to 2008 but that will go up to 2012 in the next release. Last but not least, it is not a bad idea to read some documentation, too ;) |
There are 2 targets platforms of Poco under a Window system: either using Cygwin but the whole application using Poco will be a Linux based application running above Windows within the Cygwin container either using VisualStudio and native Win32/x64 API and the whole application will be a WIndows aplication The error you reported: shows that you are using/compiling your application using the Cygwin distribution but targeted to a Windows platform which cannot work. Have a look into |
Ok, I understand the error now, and yes that's what I'm doing @zosrothko, so I'm going to try to compile with VS. Thanks |
Hi, so I try to build Poco in the Command Prompt of Visual Studio. But I'm getting an error with the WinTestRunner_x64_vs100.vcxproj
Again not idea why I'm getting this error, I try removing CppUnit and CppUnit\WinTestRunner from the components file but I kept getting the same error. |
Check your environment: VS2012 RC installation breaks VS2010 C++ projects |
Ok I'm going to check that, one quick question, Poco could be build in Visual Studio 2015 ?? or what it's the newest version of VS that supports poco ?? |
2015 is fine, although all versions back to 2008 work. |
I was seen which file to run in VS 2015 to compile poco, I was thinking about using the buildwin.cmd and pass the parameters, because I don't seem to find the one for VS 2015, so it will be something like this
it's this the correct way to do it for VS 2015 ?? Because I try to compile it in VS 2010 but it didn't work with Qt creator and c++14 when I added the libs. So I'm not sure if it was something I did in the compilation. |
You can also install poco-1.6.1 with the VS2013 msi installer located here |
No matter how I compile poco I'm still getting the same error when I try to run my qt project.
I compile poco with VS2015 and got this error, then I try with the .msi that @zosrothko suggested and got the same error. It's there a problem with qt creator and poco (for windows)?? |
Those are all defined/declared in <float.h> and poco obviously has no problem finding them. This is probably a question for QT forum, but I'd suggest to make sure that your build environment sees |
the same question $ gcc -v |
I solved this issue, using this UNdefinition: |
@DaJunkie What do you mean by "This hurts a lot."? |
@zosrothko I do not want to do things like that. It feels wrong. It is against my sense for aesthetics. Not meant offending. I would be lucky if you could find some better solution. iirc I did not need to do that in Poco 1.4.6p4. And I just read this: "Written in efficient, modern, 100% ANSI/ISO Standard C++." I think this not anymore correct. |
I'm having the same error trying to compile Poco 1.7.4 using Borlands CLANG compiler. Any pointers how to get past this error? I tried the undef mentioned above but that did not work. |
Thank you, @DaJunkie. It looks like the standard library became more strict after enabling C++11 standard. |
Hi,
I have a project in Qt that works perfectly with Poco libs on linux, I needed to test this project on Windows, so I install Poco on Windows (Virtual Machine).
First I use Cygwin to compile it and the installation ended perfectly with no error what so ever, how ever when I try to run my project I got so errors that let me believe that something when wrong during the installation of Poco.
Here are the errors I'm getting
I also compiled with MinGW, same-thing happened the instalation ended perfectly but when I try to run my project I got the same error.
Any ideas on what could be causing this error ??
The text was updated successfully, but these errors were encountered: