[Shen Wu]

Hello, I am trying to use a UDF library created for Linux system, and I want to transfer it to Windows system.
I failed to compile it some time in VS2019 following the UDF manual 3.0 based on my src and include folders, so I wonder how to finish it, or is there anything new in the UDF manual 3.2 document?

[kwhyte]

Hi Shen,
I have a few questions for you to help clarify what the problem is.
What error messages are you getting when you are trying to compile your UDF?
Is the version of CONVERGE that you are using on Windows the same as the one you are using on Linux? Also, how are you transferring your UDF library directory over to Windows? Are you just copying over the folder without rerunning the cvg_udf_init command? This will not work because the paths in, e.g, the .make and .cmake files will be out of date.

Regards,
-Killian (Applications Engineer at Convergent Science)

[Shen Wu]

Originally Posted by kwhyte

Hi Shen,
I have a few questions for you to help clarify what the problem is.
What error messages are you getting when you are trying to compile your UDF?
Is the version of CONVERGE that you are using on Windows the same as the one you are using on Linux? Also, how are you transferring your UDF library directory over to Windows? Are you just copying over the folder without rerunning the cvg_udf_init command? This will not work because the paths in, e.g, the .make and .cmake files will be out of date.

Regards,
-Killian (Applications Engineer at Convergent Science)

Dear Killian,
Sorry for the late reply.
The Converge versions in Windows and Linux are different (Linux: 3024 vs. windows 3.17). Following the steps in UDF Manual 3.0, I just copy the .src and .includes folders to Windows and run the converge_udf.dll so these paths are invalid. so I wonder how can I set new path. Can I find something new from the UDF Manual 3.2?
And if it is possible to convert this .so to .dll without original .mpp documents?
Thank you very much!

Regards,
Shen WU