Build solver error

Hello engineer, I encountered an error in the solver while building and running a simple example, and the construction was unsuccessful
The content is as follows
E:\MFIX_anli\BPN\USR_RATES .f:57: Error: Can’t open included file ‘species.inc’
CMakeFiles\udfs.dir\build.make:74: recipe for target ‘CMakeFiles/udfs.dir/E_/MFIX_anli/BPN/USR_RATES_.f.obj’ failed
mingw32-make.exe[2]: *** [CMakeFiles/udfs.dir/E_/MFIX_anli/BPN/USR_RATES_.f.obj] Error 1
CMakeFiles\Makefile2:100: recipe for target ‘CMakeFiles/udfs.dir/all’ failed
mingw32-make.exe[1]: *** [CMakeFiles/udfs.dir/all] Error 2
Makefile:134: recipe for target ‘all’ failed
mingw32-make.exe: *** [all] Error 2

BPN.zip (5.3 KB)
Please provide guidance

I checked and modified the model and code, but I still generated the ‘specialties. inc’ file when building the custom solver

[ 99%] Built target mfixcore
[ 99%] Generating species.inc
Processing chemical reaction data from Biomass.mfx…
done
[100%] Building Fortran object CMakeFiles/udfs.dir/E_/MFIX_anli/Biomass/usr_rates.f.obj
[100%] Built target udfs
[100%] Merging UDFs into libfmixcore
r - E:/MFIX_anli/Biomass/build/CMakeFiles/udfs.dir/E_/MFIX_anli/Biomass/usr_rates.f.obj
[100%] Built target Merge_UDF
[100%] Building Fortran object CMakeFiles/mfixsolver_ext.dir/model/dummy.f.obj
[100%] Linking Fortran shared library mfixsolver.so
[100%] Built target mfixsolver_ext

mode.zip (6.8 KB)

  1. Why is your file called USR_RATES .f (with an extra space before the .f)?

  2. The file is called species.inc not specialities.inc and it is supposed to be generated when building custom solver.

  3. If you have trouble with building solvers, please enable “Verbose build output” in the build popup as is suggested:

shot-2024-10-16_18-29-21

  1. When submiting bug reports, please use Submit bug report instead of creating your own .zip file. This will include more information, like the build.log file. If you are unable or unwilling to do that, please attach the full build log, not just the last part of it. Copy/paste the entire window contents, or better yet, attach the build.log file.

Thanks,

– Charles