CopperSpice Forum

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 ...

Can you let us know if you are using MSVC or MinGW on Windows. Also, which version of CMake are you using. Did you download CMake from Kitware or was this bundled with some other product. Did you build CS or install our binary files? If you are building CS from source can you let us know what option...

CopperSpice 1.9.2 was released on September 24 2024 This release includes a complete redesign of the debug build process and debug message formatting, improvements to how OpenGL is initialized on Windows, multiple changes to support CS Designer, enhancements to our CopperSpice build files, corrected...

Thanks for reaching out to the CopperSpice team. The current CopperSpice Windows platform plugin file is called CsGuiWin1.9.dll . This plugin must be located in a folder named platforms which is located in the same directory as your executable. Based on the message reported, it is likely you did not...

Thanks for bringing this up. We do agree support for Wayland would be worthwhile. It is on the roadmap and will happen sometime after we move to C++20, which is slated for the end of this year.

Barbara

David, Thanks for your questions. I have downloaded the signals and slots from github. Just so we are on the same page, can you let us know what you downloaded? The ways I have tried get activate() Signal parameter mismatch. Please tell us what you are trying to implement and a sample of the code yo...

This macro was removed in favor of a using declaration. // Q_DECLARE_FLAGS(enumName, flagName) using flagName = QFlags<enumName>; // Q_DECLARE_FLAGS(Option, OptionFlags) using OptionFlags = QFlags<Option>; Thanks for letting us know about the documentation issue and please continue to tell us about ...