Build the Visual Studio project file

[lzh-maker]

Hello everyone,
I want to debug the engine project using Visual Studio under Windows, but I don't successfully generate the project file. I want to ask you that I used two ways to generate the project file, the first is to use build_script.sh, the input parameter is -arch=win64, but this method does not generate VS project file, but generates a makefile file; The second way is to use cmakegui and choose to generate Vs2019 project files, but the error ERROR is reported during the cmake process: -mpi= not available for this platform, do I have to install mpi to build? I'm confused about generating vs project files, is there a small partner who has successfully generated, can you share the experience?

[lzh-maker]

I rebuilt it with cygwin, and the problem in this image appears, is this because of the low oneAPI version?

[OlivierWienholtz]

Hello,

I'll go through your questions :

We encountered several issues with OneAPI versions prior to 2023.0.0.
I recommend to use OneAPI 2023.0.0 which is the latest available version...

but it should have compiled.
You can add '-verbose' to build_script in order to dump verbose commands to the Makefiles.
I suspect Cygwin/Cmake to have troubles with 'special characters' like th '@' in your path.

[OlivierWienholtz]

The build method with offer is dedicated to Unix & Co Tools (cygwin for windows native builds).
It is true that we don't offer native VS vcproj or MS-Build yet.

The build with cmakegui is an option, pls add : mpi=none in the cmake configs.
IMO : there are several tasks to perform to have a native Windows build.
The build method implemented in Cmake is using Perl to generate some includes.
I doubt this is natively available on Intel Compiler / VS...
Those needs to to be rewritten/Ported to something more generic.

[lzh-maker]

I uninstalled the previous oneAPI and reinstalled a 2023.0 version, using "build_script.sh" to compile, plus the parameters "-verbose and -debug=1", and I still get the following error, I have mingw-win64 on my computer, I have a little question, will gfortran in mingw affect compilation? Will it conflict with gfortran in oneAPI?

[lzh-maker]

The symbol @ in the path has also been removed

[lzh-maker]

I also have a puzzle point, isn't the build result of the "build_script.sh" tool using -arch=win64 under windows in VS project file .sln format? My actual goal is to generate VS2019 project files, so that I can compile and debug under Windows more easily, so that I can better understand the code, can you tell me how to achieve my goal

[OlivierWienholtz]

Hello,

There is an issue in the script when 2 compilers are set & running eg : Intel OneAPI + MinGW.
I am looking to fix this.
For the time being I recommend to remove the PATH to cygwin, on Order Cygwin sees only Intel OneAPI.

I'll keep you informed.

On the other topic, I am currently checking what needs to be done to create svn or MSBuild files from Cmake but there might be some changes in our build scripts & methods to achieve this.