<![CDATA[Multiwfn forum / dislin module name]]> http://sobereva.com/wfnbbs/viewtopic.php?id=769 Sun, 05 Feb 2023 18:44:20 +0000 FluxBB <![CDATA[Re: dislin module name]]> http://sobereva.com/wfnbbs/viewtopic.php?pid=2951#p2951 I agree with you. I just updated Multiwfn source code package on the website, now all "use dislin_d" in source code have been changed to "use dislin", and all "dislin_d.mod" in Makefile has been changed to "dislin.mod".

]]> Sun, 05 Feb 2023 18:44:20 +0000 http://sobereva.com/wfnbbs/viewtopic.php?pid=2951#p2951 <![CDATA[dislin module name]]> http://sobereva.com/wfnbbs/viewtopic.php?pid=2948#p2948 I ran into some compilation issues with my CMake build script for the Mac build, due to the discrepancy between the module name of dislin in dislin_d.f90 ("dislin") and the imports in other files ("use dislin_d"). In your makefile, I believe this is currently obscured by the rule to create the mod-file dislin_d.mod from the source file dislin_d.f90:

dislin_d.mod : dislin_d.f90
    $(FC) $(OPT) -c dislin_d.f90

For consistency and portability I would suggest to either:
1. Change the module name to "dislin_d"
2. Change the imports and the Makefile rule to use "dislin"

https://github.com/kjelljorner/multiwfn … eLists.txt

]]> Sun, 05 Feb 2023 10:11:41 +0000 http://sobereva.com/wfnbbs/viewtopic.php?pid=2948#p2948