CopperSpice Forum

You actually can not be using MinGW without access to a certain set of files. As I mentioned, you are most likely compiling with some parts of our distribution of MinGW and some files from cygwin. This could result in binary incompatibilities and is not advisable. This is a problem waiting to happen...

Several of the files you listed are used by MinGW during the compile and link process. Since you removed some required files MinGW must be finding a program with the same name from your copy of cygwin. Their version and the one we distributed are probably not binary compatible. Sadly this is the typ...

I wanted to mention two things just in case this helps you out. 1) We understand there are still warnings on some platforms. MSVC has more than others, some have almost none. Our team spends time resolving these and over time the number has reduced. As newer compilers are released some things which ...

Just to be clear, you are looking for a distribution which only contains the MinGW compiler and GDB? This is not impossible, however it will require some testing since the compiler has multiple dependencies.

We have added this to our road map.

Barbara

Thanks for reaching out to us. Can you confirm, you were able to build CopperSpice with no errors but you had a few warnings. Is this correct? It is an on going process to remove warnings. Newer versions of platforms and C++ compilers will flag new warnings. Please continue with the installation and...

We are not sure what you mean by "separating all those libraries". There is nothing to separate. In our CI we have the Release and Debug builds in separate directories with zero issues. The source is in one location and we have multiple build directories and multiple install directories. F...

Installing Release and Debug builds in the same location is not a supported configuration for MSVC. A suffix on the library names is not sufficient to resolve potential conflicts between the installed files. For example, you need the correct version of UIC, RCC and the exported CMake files. Instead,...

There is no standard structure for Windows and projects are free to set their own requirements. Windows developers generally expect a more flat directory structure than Unix developers. We have documented our file layout in the CS Overview documentation and our CS Journal. Just for reference, these ...

Are you using MSVC or MinGW on Windows?

My local CMAKE_PREFIX_PATH is "d:\code\third_party\usr\local". For reference, CopperSpice downstream projects on Windows using both MSVC and MinGW have been fully tested in our CI. Applications like KitchenSink, Diamond, and DoxyPress are all working with the current path structure. Your ...