Copperspice and VS 2022
Posted: Wed Oct 23 2024 7:28 pm
Hi all,
I am trying CopperSpice on Windows 11 Pro but I am probably making something wrong.
Here is what I did, step by step, mostly following your instructions (for VS 2019, I know) here: https://www.copperspice.com/docs/cs_overview/build-msvc.html
- Launch my Visual Studio 2022 community edition
- Choose "Clone a repository"
Repository location: https://github.com/copperspice/copperspice.git
Path: C:\copperspice
- Right click on CMakeLists.txt, CMake settings for copperspice
- Add x64-Release configuration
- Save to CMakeSettings.json
- Menu bar: Build|Build all
Build succeeds with 0 errors but:
- one Warning C4244 'argument': conversion from 'qint64' to 'double', possible loss of data
and
- 45694 (!) warnings C4291 similar to this one:
'void *QTJSC::UStringImpl::operator new(size_t,void *)': no matching operator delete found; memory will not be freed if initialization throws an exception
Should I go on, install, and try some example, or there is some incompatibility with VS 2022?
Best regards,
Daniele
I am trying CopperSpice on Windows 11 Pro but I am probably making something wrong.
Here is what I did, step by step, mostly following your instructions (for VS 2019, I know) here: https://www.copperspice.com/docs/cs_overview/build-msvc.html
- Launch my Visual Studio 2022 community edition
- Choose "Clone a repository"
Repository location: https://github.com/copperspice/copperspice.git
Path: C:\copperspice
- Right click on CMakeLists.txt, CMake settings for copperspice
- Add x64-Release configuration
- Save to CMakeSettings.json
- Menu bar: Build|Build all
Build succeeds with 0 errors but:
- one Warning C4244 'argument': conversion from 'qint64' to 'double', possible loss of data
and
- 45694 (!) warnings C4291 similar to this one:
'void *QTJSC::UStringImpl::operator new(size_t,void *)': no matching operator delete found; memory will not be freed if initialization throws an exception
Should I go on, install, and try some example, or there is some incompatibility with VS 2022?
Best regards,
Daniele