Need Help with Toolkit

[Askarke]

I was following Getting Started with Creo Parametric Toolkit but something failed and I don´t know how to solve it.

I tried to open make_install.sln through Visual Studio 2022 and build the solution, but an error occurred.
It says "Cannot open include file: 'stdio.h'".

I searched info about that bug and tried many things like uninstall VS, install other libraries. However, nothing works.
I also built "Hello World" in VS to check if "stdio.h" is avalaible, and nothing failed.

I will really appreciate if someone could help me.

Thanks!

[Askarke · Accepted solution]

It´s working now. I have included every single header and library manually,but now it works

[Theron]

I had this issue, was able to resolve it by adding the stdio.h path to the project in the Include Directories... "C:\Program Files (x86)\Windows Kits\10\Include\10.0.22621.0\ucrt"

After is error was resolved I need to Library paths also...
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\um\arm64

C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\ucrt\arm64

[Matt_Huybrecht]

Just to follow up on this issue. I had the same problem with the stdio.h file not being found.

I used Theron's additions listed above adding the paths. Only difference for me is that my machine is x86 so latter 2 paths were just a bit different:

C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\um\x64

C:\Program Files (x86)\Windows Kits\10\Lib\10.0.22621.0\ucrt\x64

Once I did that my build succeeded.

[PH_10785300]

Will you please help me how you linked creo to visual studio. Please explain point by point it will help me in lot of things.

[lcook]

What was the fix? I'm not seeing it. I'm getting the same error and I'm not sure what everything was you added.

[Askarke]

Sorry mate, It's been too long and I don't even remember the problem I had.

With my license, Creo Toolkit is not available so I removed it from my Creo Parametric Customisation and I can't even check it to help you more.

I wish I could help you better than I did.

[lcook]

No problem, thanks for replying. 🙂