This is how the Cmake writes the ALL_BUILD.vcxproj file.Īfter doing all the above the code All_Build target runs well and compiles. This is needed because the produced fortran obj files retain inside them ".f90" and be in form "fcvode_". For example the the fcvode_mod.f90 must be renamed to fcvode_90. f90 files must be renamed to duplicate their extension. The location of these objects is changed to the output of the custom Fortran project.Ī trick needed above is that all. For example the "sundials_fcvode_mod_static" contains many objects like "fcvode_", fnvector_serial_ and so on. Furthermore all "._mod_static" targets must have all their "._" objects change their location and point to the output directory of the Fortran project created above. f90 files must be created and then added to the current project created from Cmake in Build_dir. As very well stated here in order for the compilation to succeed a Fortran project containing all. The reason for this kind of errors after lots of search, is caused because the visual studio 2013 & 2019 cant handle a mix C and Fortran files in same project. The compiling stops with errors of the type:Įrror LNK1181 cannot open input file 'C:\Users\.\build_dir\src\sunmatrix\band\fmod\sundials_fsunmatrixband_mod_obj_static.dir\Debug\fsunmatrix_band_' sundials_fsunmatrixband_mod_staticĜ:\Users\.\build_dir\src\sunmatrix\band\fmod\LINKđ The problems start after I open the project and try to build the "ALL_BUILD" target. After pressing generate, the Visual studio 2019 project is being build.The Fortran compiler identification is Intel 2021.0228ĭetecting Fortran compiler ABI info - doneĭetermine Intel Fortran Compiler Implicit Link Pathĭetermine Intel Fortran Compiler Implicit Link Path - doneĬheck for working Fortran compiler: C:/Program Files (x86)/Intel/oneAPI/compiler/2021.2.0/windows/bin/intel64/ifort.exe - skippedĬhecking whether C:/Program Files (x86)/Intel/oneAPI/compiler/2021.2.0/windows/bin/intel64/ifort.exe supports Fortran 90Ĭhecking whether C:/Program Files (x86)/Intel/oneAPI/compiler/2021.2.0/windows/bin/intel64/ifort.exe supports Fortran 90 - yesĬhecking whether C:/Program Files (x86)/Intel/oneAPI/compiler/2021.2.0/windows/bin/intel64/ifort.exe supports F2003Ĭhecking whether C:/Program Files (x86)/Intel/oneAPI/compiler/2021.2.0/windows/bin/intel64/ifort.exe supports F2003 - yes Cmake now locates the Intel compiler properly: I select only the CVode and Build_Fortran_Module_Interface and I deselect everything that has to do with testing and examples. The Cmake finds all the Sundial 5.7 source (Arcode, CVode.).Performing Test COMPILER_HAS_DEPRECATED - Success Performing Test COMPILER_HAS_DEPRECATED_ATTR - Failed Performing Test COMPILER_HAS_DEPRECATED_ATTR
The C compiler identification is MSVC 0.0Ĭheck for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/7/bin/Host圆4/圆4/cl.exe - skipped
Thank you very much for your kindly attention.Selecting Windows SDK version 1.0 to target Windows 2. The problem come when I apply for Twisted 2D-Beam, Feap 8.3 give wrong result compare to feap 7.1.is there anyone has solution for problem above? Nevertheless Feap 7.1 never show the statement above. >Element 0 Reverse numbers to fix negative jacobian >Element 0 has zero or negative jacobian at nodes: In migrating from feap 7.1 to Feap 8.3, I just change the code in definition of material (Inpt2d become Inmate) and loading intensity (d10 become d8).įor case Parabolic-Hyperbolic, Spherical Dome, Cylindrical Shell Roof, Circular Cylindrical Shell, Both of Feap 7.1 and Feap 8.3 with the same user element (MITC24) definitely give the same result although in ouput file in Feap 8.3 is always show I am apply user element for shell element MITC24 in FEAP 7.1 and FEAP 8.3.