-
Notifications
You must be signed in to change notification settings - Fork 14
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.
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
rebuild plugin upon library changes #252
Comments
This may be a fix. It adds in a an extra file under I had initially wanted to use the version of the installed library, but that gets written to each time since currently invoking |
Off the top of my head, I don't think I have any objections to this. The problem you're trying to solve is a problem caused by This seems like a simple and clean way of accomplishing (ii). It's just a humble file, which doesn't intrude upon any of the other workings of anything. It can be removed easily if we ever get a better solution. Anybody else have any thoughts? |
I also have no objections! The change is very clean, and easy to read too. |
closed with #255 |
Based on this, when a library dependency to a binary is updated, the binary is not relinked to support the new library. The solution here is, when the plugin is changed, to
clean
the plugin directory, then rebuild. This forces linking to the new version of the library. To accomplish this, we can watch the library from the root makefile, and on a change to that file,-clean
the plugin before rebuilding.The text was updated successfully, but these errors were encountered: