UDF compilation error/'stdio.h': No such file or directory/ VS variables

alinik · April 23, 2019, 16:36

Hi all,

I have Fluent 19.1 and Visual Studio 2017 Professional.
Yet, I cannot compile any UDF codes.
According to ANSYS tech support, for VS 2017, I shall not manually alter the Path variable or create INLCUDE or others. According to them, the following variables must be populated in VS command prompt when I type ": set", and I am missing all of them. Apparently, they have to be created automatically and I must not manually add them.

WindowsSdkBinPath=C:\Program Files (x86)\Windows Kits\10\bin\
WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\
WindowsSDKLibVersion=10.0.16299.0\
WindowsSdkVerBinPath=C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\
WindowsSDKVersion=10.0.16299.0\
WindowsSDK_ExecutablePath_x64=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\
WindowsSDK_ExecutablePath_x86=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\

Has anyone had this issue before?
Has anyone used Fluent 19.1 and VS 2017 successfully with one-another before?
Please advise.

Svetlana · April 25, 2019, 02:13

Are ansys tech support not able to resolve this issue?

alinik · April 29, 2019, 12:36

No, they are clueless.
They keep saying it is Windows fault and is due to improper installation of Visual Studio and/or windows. My IT people refuse to accept that reason.

Svetlana · April 29, 2019, 22:06

I would suggest the ansys technical people to detail what are the specific problems with the install. Then share these problems with your IT.

April 23, 2019, 16:36	UDF compilation error/'stdio.h': No such file or directory/ VS variables	#1
alinik Senior Member ali Join Date: Oct 2009 Posts: 318 Rep Power: 18	Hi all, I have Fluent 19.1 and Visual Studio 2017 Professional. Yet, I cannot compile any UDF codes. According to ANSYS tech support, for VS 2017, I shall not manually alter the Path variable or create INLCUDE or others. According to them, the following variables must be populated in VS command prompt when I type ": set", and I am missing all of them. Apparently, they have to be created automatically and I must not manually add them. WindowsSdkBinPath=C:\Program Files (x86)\Windows Kits\10\bin\ WindowsSdkDir=C:\Program Files (x86)\Windows Kits\10\ WindowsSDKLibVersion=10.0.16299.0\ WindowsSdkVerBinPath=C:\Program Files (x86)\Windows Kits\10\bin\10.0.16299.0\ WindowsSDKVersion=10.0.16299.0\ WindowsSDK_ExecutablePath_x64=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\ WindowsSDK_ExecutablePath_x86=C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\ Has anyone had this issue before? Has anyone used Fluent 19.1 and VS 2017 successfully with one-another before? Please advise.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[swak4Foam] swak4foam for OpenFOAM 4.0	mnikku	OpenFOAM Community Contributions	80	May 17, 2022 09:06
how to calculate mass flow rate on patches and summation of that during the run?	immortality	OpenFOAM Post-Processing	104	February 16, 2021 09:46
[swak4Foam] funkyDoCalc with OF2.3 massflow	NiFl	OpenFOAM Community Contributions	14	November 25, 2020 04:30
centOS 5.6 : paraFoam not working	yossi	OpenFOAM Installation	2	October 9, 2013 02:41
[swak4Foam] build problem swak4Foam OF 2.2.0	mcathela	OpenFOAM Community Contributions	14	April 23, 2013 14:59

April 25, 2019, 02:13		#2
Svetlana Senior Member Svetlana Tkachenko Join Date: Oct 2013 Location: Australia, Sydney Posts: 416 Rep Power: 15	Are ansys tech support not able to resolve this issue?

April 29, 2019, 12:36		#3
alinik Senior Member ali Join Date: Oct 2009 Posts: 318 Rep Power: 18	No, they are clueless. They keep saying it is Windows fault and is due to improper installation of Visual Studio and/or windows. My IT people refuse to accept that reason.

April 29, 2019, 22:06		#4
Svetlana Senior Member Svetlana Tkachenko Join Date: Oct 2013 Location: Australia, Sydney Posts: 416 Rep Power: 15	I would suggest the ansys technical people to detail what are the specific problems with the install. Then share these problems with your IT.