Building with Visual Studio

Install requirements

• The latest Microsoft Visual Studio (Preview) from https://visualstudio.microsoft.com/ with the following options installed:
  • C++ core desktop features
  • C++ CMake tools
  • Test Adapter for Google Test
  • Windows 10 (or newer) SDK
• git from: https://git-scm.com/
• The Vulkan SDK from: https://www.lunarg.com/vulkan-sdk/ with the following options installed:
  • The Vulkan SDK Core (Always Installed)
  • Vulkan Memory Allocator header.
• optional: RenderDoc (for Vulkan debugging) from: https://renderdoc.org/
• optional: Doxygen (for documentation generation) from: https://www.doxygen.nl/

Clone the HikoGUI project from github

Clone the HikoGUI repository on your machine:

git clone git@github.com:hikogui/hikogui.git

Building and running

You can then open the hikogui directory as a directory-based project inside visual studio.

To build:

1. Select x64-MSVC-Debug from the project Configuration pull down menu.
2. Project / Generate Cache menu option
3. Build / Build All menu option
4. Select hikogui_demo.exe from the Select Startup Item... pull-down menu.
5. Select Build Only in the Error List window to ignore IntelliSense false positives.
6. Debug / Start Debugging

Note: A "Window Security Alert" may show up, this is due to the RenderDoc API creating a network server so that the RenderDoc application can remotely communicate to the hikogui_demo application.

Other configurations that are possible to build:

• MSVC-x64-Debug Make a debug build
• MSVC-x64-RelWithDebInfo Make an fully optimized build
• MSVC-x64-Release Make a fully optimized build and build all examples and demos.
• MSVC-x64-Analysis Build with static-analysis.

Common build problems:

• When Visual Studio gets confused try deleting the CMake cache using the Project / Delete Cache and Reconfigure menu option.
• If you get "permission denied", this may be due to a still running process like a hung hikogui_test.exe. Terminate that process using the Task Manager.
• You may also get "permission denied" when during building a compiler-crash causes a file to be written without any permissions associated at all. This can be solved by rebooting the computer and followed by deleting the CMake cache.
• The Test Explorer may get confused as well, try deleting the cache in: hikogui\.vs\v17\TestStore\0\*.testlog.

Building and running using the "x64 Developer Command Prompt"

cd hikogui
mkdir build
cd build
 
cmake .. -DCMAKE_VERBOSE_MAKEFILE=ON -DBUILD_SHARED_LIBS=OFF
 
cmake --build . --config Debug
 
cmake --install . --config Debug --prefix install

install\tests\hikogui_tests.exe
 
install\examples\hikogui_demo\hikogui_demo.exe

_note: The "Developer PowerShell for VS 2022" always runs the x86 compiler which you can not use. Instead first start the "x64 native Tools Command Prompt for VS 2022" then execute "start powershell" from there to get the correct compiler for x64." @section autotoc_md88 Just-in-time debugging with Visual Studio When a HikoGUI application hits a break-point while not running with a debugger the Windows 10 CRT will try to start the just-in-time debugger as a fallback. A common problem in Windows 10 are the missing registry entries for the JIT-debugger to work. The fix is to add a <tt>DWORD Value</tt> of <tt>Auto</tt>, with <tt>Value data</tt> of <tt>1</tt>, to the following registry keys: * <tt>HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug</tt> - DWORD "Auto" : Value (1) * <tt>HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug</tt> - DWORD "Auto" : Value (1) See <a href="https://docs.microsoft.com/en-us/visualstudio/debugger/debug-using-the-just-in-time-debugger?view=vs-2022" >Just in Time debugging.

Note due to bugs in IntelliSense you will get JIT-debugger prompts for Visual Studio itself. This does allow you to create crash-dumps for Visual Studio and its components to report bugs with Microsoft.