Not able to create cef.sln with branch 6045

[samohtt]

Usually we download the standard distribution packages for Win 64-Bit and Win 32-Bit from the spotify build server, then we change the runtime flag from /MT to /MD in cef_variables.cmake and then we create cef.sln in a command prompt via cmake.
With this solution we build the libcef_dll_wrapper project and use this for our project.
This worked fine until branch 5993, but is not possible with branch 6045.

Here is the output of the command prompt on exactly the same machine with cmake version 3.28 and Visual Studio 2022 17.7.4

Code: Select all

C:\CEF\cef_binary_118.7.1+g99817d2+chromium-118.0.5993.119_windows64\build>cmake -G "Visual Studio 17 2022" -A x64 ..\
-- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
-- The C compiler identification is MSVC 19.37.32824.0
-- The CXX compiler identification is MSVC 19.37.32824.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- *** CEF CONFIGURATION SETTINGS ***
-- Generator:                    Visual Studio 17 2022
-- Platform:                     Windows
-- Project architecture:         x86_64
-- Binary distribution root:     C:/CEF/cef_binary_118.7.1+g99817d2+chromium-118.0.5993.119_windows64/cef_binary_118.7.1+g99817d2+chromium-118.0.5993.119_windows64
-- Visual Studio ATL support:    ON
-- CEF sandbox:                  ON

Code: Select all

C:\CEF\cef_binary_119.2.1+gf2646ea+chromium-119.0.6045.105_windows64_beta\build>cmake -G "Visual Studio 17 2022" -A x64 ..\
-- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
-- The C compiler identification is MSVC 19.37.32824.0
-- The CXX compiler identification is MSVC 19.37.32824.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/Program Files/CMake/share/cmake-3.28/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'C:/CEF/cef_binary_119.2.1+gf2646ea+chromium-119.0.6045.105_windows64_beta/cef_binary_119.2.1+gf2646ea+chromium-119.0.6045.105_windows64_beta/build/CMakeFiles/CMakeScratch/TryCompile-2mdejh'

Something is wrong in the compiler detection with branch 6045. As this is exactly the same environment and only different branches I think I can exclude my machine environment as the root cause.
There are some other posts in the last few days regarding build errors but this seems to be more cmake configuration related. I cannot find any difference of the cmake files in the latest branches, so I have no idea what's going on here.

Anybody else with the same problem ? Any idea how to solve this ?

[magreenblatt]

Cmake 3.28 is a release candidate currently. What cmake version were you using previously?

[ndesktop]

3.28 gave me some headaches as well. I am using 3.27.4 without problems.

[magreenblatt]

It fails with the following output:

Change Dir: 'C:/CEF/cef_binary_119.2.1+gf2646ea+chromium-119.0.6045.105_windows64_beta/cef_binary_119.2.1+gf2646ea+chromium-119.0.6045.105_windows64_beta/build/CMakeFiles/CMakeScratch/TryCompile-2mdejh'

Have you enabled long file paths on your system? https://www.howtogeek.com/266621/how-to ... haracters/

[samohtt]

I think I had previously 3.17 and made the change to 3.28 after the problem occurs, just to test if this is cmake related problem.
I will check with 3.27 and come back with the test results later.
Thanks for the hint with the long paths, I don't think that this is the root cause, because usually I have smaller path names.
The posted console output was just to test quickly with the latest available distribution packages and I just extracted everything into the same folders. It also works fine for the 5993 branch where the path is roughly the same.

[samohtt]

Have you enabled long file paths on your system? https://www.howtogeek.com/266621/how-to ... haracters/

I have to admit...you are absolutely write. The long path is the problem and not something else.
I installed cmake 3.27.7 but had the same error result and then I changed the folder names to something shorter and suddenly it worked fine.

The difference to the 5993 branch is that 6045 currently has the extension "_beta" and with this it seems to overflow the internal path limit with the compiler test run. Without the "_beta" extension everything works fine also with the 6045 branch.
So, I will change my folder structure in the future without using the long names when extracting the distribution package.

Thank you for giving me the crucial hint.