Rebar3

[sargun]

Do you have this working on a rebar3 compiled project? I'm seeing some issues with this where it can't find the source files.

[choptastic]

I've not yet started testing this with rebar3, but I'm very open to a pull
request.

Mostly suspect that the problem lies in the ambiguity of the source
location due to rebar3's use of symlinks, if I remember correctly.

Jesse Gumm
Owner, Sigma Star Systems
414.940.4866 || sigma-star.com || @jessegumm
On Nov 27, 2015 12:22 AM, "Sargun Dhillon" [email protected] wrote:

Do you have this working on a rebar3 compiled project? I'm seeing some
issues with this where it can't find the source files.

—
Reply to this email directly or view it on GitHub
#63.

[nuex]

@sargun in the meantime, i've had success using the rebar3_auto plugin: http://blog.erlware.org/rebar3-auto-comile-and-load-plugin

[stuart-thackray]

Hi,

I am happy to make a the pull request for this if there is a suggested way it should work. There is rebar3 auto; has two features I don't like a dependency to install a library on linux & the fact that it recompiles everything this is especially a problem when there are over 1000 (actual case) files for a node.

From what I have been able to see is the fact that rebar3 just moves all files from it app to its

_build/PROFILE/lib

directory (no sym links that i have seen) therefore the source directories reported by modules is in that directory not the apps/ directory. Therefore changes are not picked up.