Forums | NoesisGUI

Hi,

I'm considering using NoesisGUI on a project and am taking a look at the samples provided with the native SDK.
But I'm a bit confused about the intended way of building them.

If I open NoesisGUI-win-x86_64.sln on VS2022 (Windows 10), and try to build the solution, or any non-blend project, the building fails with error:

C1083 Cannot open include file: 'pch.h': No such file or directory.

However, If I try to build any -blend projects they run fine.

Now, if I clean the solution, open it on Blend, and try to build it there the exact same way as VS, all the 49 projects build fine.
If I then try to build the solution on VS, I get that 26 projects succeeded (non-blend projects?) and that 23 are up-to-date.
I can then execute any project on the solution from that point on.

I'm a bit confused about this behaviour.
Is this the intended way of building the solution for these samples, or did I miss something in the docs?

Is this Noesis 3.2.0? Because, we don't have NoesisGUI-win-x86_64.sln in that version. You have a solution for each version of Visual Studio:

• NoesisGUI-win-x86_64-vs2015.sln
• NoesisGUI-win-x86_64-vs2017.sln
• NoesisGUI-win-x86_64-vs2019.sln
• NoesisGUI-win-x86_64-vs2022.sln

Opening the corresponding solution and doing "Build All" should generate all examples without errors. Support for Visual Studio 2022 was recently added, so there could be issues, I will verify everything is correct. Meanwhile you could try with the 2019 solution, Visual 2022 will upgrade it.

I re-tested the following solutions, from our latest 3.2.0 release, on a fresh install of Visual Studio 2022. I found no issues.

• Build\NoesisGUI-win-x86_64-vs2022.sln
• Build\NoesisGUI-win-x86-vs2022.sln

Could you verify that you are using the latest 3.2.0 release? We did not officially support Visual Studio 2022 prior to 3.2.

jsantos, maherne,

Thank you for the quick feedback!
I was using NoesisGUI-win-x86_64-vs2022.sln, in the lastest 3.2.0 version indeed. The same problem happened in vs2019 version too.

After some more extensive testing I was able to track down the problem to distributed building.
I use Sony's SN-DBS tool to speed up the building process in my projects, and it appears that enabling it causes the problem I described in the first post.
(maybe something regarding the order that the projects need to be built in this solution?)
After turning distributed building off, I was able to build it without any problems, in both 2019 and 2022 version.

I should be able to proceed now with evaluating the samples/integration docs.
Many thanks!

Great! Marking this as solved