You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-5Lines changed: 13 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -524,16 +524,24 @@ Use the `dialyzer` task to check applications for type discrepancies. To use the
524
524
$ rebar3 atomvm dialyzer
525
525
```
526
526
527
-
This task requires a complete AtomVM installation. This includes the AtomVM binary, the standard atomvmlib libraries, compiled beam files, and the `atomvm`
528
-
launcher script. The `atomvm` launcher script should be in your PATH. This is all taken care of with a MacOS install using MacPorts, or Homebrew.
529
-
Linux users will need to build from source and use the cmake "install" target. If you have "installed" AtomVM to a non-standard location (i.e. /otp/atomvm)
530
-
and the `atomvm` launcher script is not in your PATH you must supply the install location containing the AtomVM libraries using the `--atomvm_root` option
531
-
when using this task. For example:
527
+
The `atomvm` launcher script should be in your PATH. This is taken care of with a MacOS install using MacPorts, or
528
+
Homebrew. Linux users will need to build from source and use the cmake "install" target. If you have installed AtomVM
529
+
to a non-standard location (i.e. /otp/atomvm) and the `atomvm` launcher script is not in your PATH you must supply the
530
+
install location containing the AtomVM libraries using the `--atomvm_root` option when using this task. You may also
531
+
use the path to the build directory used for a generic_unix build of the AtomVM BEAM libraries.
532
+
533
+
Example for a non-standard instal when `atomvm` launcher is not in PATH:
0 commit comments