-
Notifications
You must be signed in to change notification settings - Fork 5
How it works ?
Eric Pailleau edited this page Mar 11, 2018
·
1 revision
Geas extract all function calls in project’s beam files where abstract code is available and compare to its database. Geas keep only the modules existing in its database, assuming other are modules created by the project. Geas search the starting and optionnaly ending Erlang release exporting thoses modules and functions/arity. Geas gives you then the compatibility with the highest minimal Erlang release and the lowest maximal Erlang release, called the release window. Geas detect native compilation that can reduce your project scattering.
Geas, by default, does not use source code for at least three reasons :
- Source code is not always available
- Source code may compile in different targets depending defines
- Native compilation cannot be detected from source