Windows Build stuck?

[mategomez9]

I've followed the guide and recommendations on this two discussions #91 and #67. and now looks like the build is stuck at [76%] Built target QtWidgets. it has not thrown any errors so far but it's been there for about 5 hours. is this normal?

I used this to build
cmake --build cmake-build --config Release --target rv -j8

Attached is some of the log output.

buildlog.txt

[mategomez9]

I was able to finally build it in a fresh install of win10

[mategomez9]

Thanks Gary, I retried the build and this time is finished with 7 errors and no executable. so I made a new system with a fresh install of win10 and that dis the trick. Thank you! On Mar 12, 2023, at 3:34 AM, Gary Warner ***@***.******@***.***>> wrote: A build process getting stuck for several hours at a specific point is not normal and could indicate that there is an issue with the build. It's possible that there is a problem with the build system, dependencies, or configuration. To diagnose the issue, you can try the following: Check the system resources: Check if the CPU, memory, and disk usage are high during the build process. If any of these resources are at their maximum limit, it can cause the build process to slow down or get stuck. Check the log output: Look for any error messages or warnings in the log output that might indicate an issue with the build process. Also, look for any clues that might suggest what the build process is currently doing. Restart the build process: If the build process has been stuck for several hours, it might be a good idea to stop and restart the process. This can help to clear any issues with the build system and dependencies. Try a different build system: If the issue persists, you can try using a different build system or configuration to see if that resolves the issue. Seek help from the community: If you're still having issues, you can reach out to the community for help. Forums, chat rooms, and other online resources can be a great place to ask for advice and troubleshoot the issue. In general, a build process getting stuck for several hours is not normal and suggests that there is an issue that needs to be addressed. — Reply to this email directly, view it on GitHub<#96 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGK2Y55K2KOUWQHXKWAOEQDW3WRDTANCNFSM6AAAAAAVUMDSH4>. You are receiving this because you authored the thread.Message ID: ***@***.***>