CFD Online Discussion Forums

CFD Online Discussion Forums (http://www.cfd-online.com/Forums/)
-   Fluent UDF and Scheme Programming (http://www.cfd-online.com/Forums/fluent-udf/)
-   -   UDF compilation through nmake (http://www.cfd-online.com/Forums/fluent-udf/112756-udf-compilation-through-nmake.html)

yorelchr February 4, 2013 19:37

UDF compilation through nmake
 
hello everyone,

I am trying to sort out problems with UDF, but no way.
I'm using FLUENT 13 and I have installed Microsoft Visual Studio 10.0
I have windows XP, 32bit.

I have encountered many problems, I could fix part of them thanks to some similar problems I have found on this forum, but it is not enough.

When opening Fluent from Microsoft Visual Studio prompt command, now I can build and load my library directly from the fluent panel. But if I do a "nmake" from the prompt, it does not work and gives me :
makefile(49): fatal error U 1050: you need to define the environmental variable FLUENT_INC. It is important for me to build the library in this way because, I will work with a UDF calling a source file in Fortran, and this can't be done through the FLuent panel.

At first, I couldn't even build and load from fluent, but I followed this :
http://www.cfd-online.com/Forums/fluent-udf/47783-about-udf-compiling-issues-nmake.html where the link http://www.cfd-online.com/Wiki/Fluen...at_is_wrong.3F explains :

Quote:

Set the correct environment variables. Browse your way through the Windows system control to 'System'. There you will find a section 'Advanced system settings'. In the following dialog go to the 'Advanced' tabulator and click on 'Environment variables' (lower right corner). Go through the 'System variables' list and search for the 'Path' entry. Add the following to the variable: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools;C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin;C:\Program Files\ANSYS Inc\v120\fluent\ntbin\win64. Adjust this entry to your system concerning the installation directories!
the only things that was not ok for me is about the last entry : C:\Program Files\ANSYS Inc\v120\fluent\ntbin\win64, I don't have any win64. And I also add : C:\Programmi\Microsoft Visual Studio 10.0\VC so the path to vcvarsall.bat script is ok (I saw that on the same link)

Maybe going back from the beginning could also be helpful:
about the directories :
My work directory should contain : *.cas, *.dat, udf.c. Should I create manually the libudf and libudf/src directories or the nmake should do it itself? about the makefile and user_nt.udf? I took them from the ANSYS Inc\v130\fluent\fluent13.0.0\src directory and modified the user_nt.udf as mentionned in the Makefile_nt.udf file that I renamed as makefile.
Is there anything else to do?

All I could read about udf in the forum couldn't give me the final solution. I also tried to run the \Microsoft Visual Studio 10.0\VC\bin\vcvars32.bat but nothing happens.

Thank you for any help!!

msaeedsadeghi February 5, 2013 01:17

Oh, it's owfull but have done that.
In 32Bit windows I prefer to use visual studio 2005, so easy to be connected with Ansys Fluent.

yorelchr February 5, 2013 09:27

thank you for your reply !!!!

Did you have anything "special" to do? edit udf.bat or something of this kind?
where should I go to define the environmental variable FLUENT_INC?

yorelchr February 5, 2013 10:03

ok, if someone is interested, I think I have the solution for the fatal error U1050 : you need to define the environmental variable FLUENT_INC

From a Microsoft Visual Studio 10.0 prompt command, I went into the \ANSYS_INC\v130\fluent\ntbin\ntx86 directory and launched setenv.exe ...I clicked on "ok" in the box that appeared. Then I re-boot the computer and now, I don't have this error message anymore; I have another one :) ... I am trying to fix it. Else, I come back here !!!

vasava March 26, 2013 09:52

About environmental variables you can run 'setenv' file to set the environmental variable. The file is in the fluent installation directory. Then launch Fluent from CMD Shell of Microsoft Windows SDK v7.0. It should work fine.

If this does not work I suggest you switch to VS2008. I have been in same mess before. Installing VS2008 got me out of it.

All the best.


All times are GMT -4. The time now is 17:00.