Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use manifest to see if a module should be compiled or not #438

Open
bryanjos opened this issue Nov 7, 2017 · 1 comment
Open

Use manifest to see if a module should be compiled or not #438

bryanjos opened this issue Nov 7, 2017 · 1 comment

Comments

@bryanjos
Copy link
Collaborator

bryanjos commented Nov 7, 2017

Using information from manifest in #435, I think we can tell if we will need to compile modules based on if timestamps changed. This issue replaces #310
@bryanjos bryanjos added this to the 0.32.0 milestone Nov 7, 2017
@bryanjos bryanjos mentioned this issue Nov 7, 2017
Closed
@bryanjos
Copy link
Collaborator Author

  • Read Manifest
  • Get manifest timestamp
  • Find removed beam files
  • Find changed beam files using path and File.stat
  • modules to be compiled will be changed - removed
  • Compile modules
  • Merge unchanged modules plus new compilation results
  • Write to manifest

@bryanjos bryanjos removed this from the 0.32.0 milestone Jan 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bryanjos