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
Problem is it depends on the keystone, capstone, unicorn triad all from git. Should we install those generically and set LD_LIBRARY_PATH so that all other tools can use it, or keep it just to the patchkit subdir?
The text was updated successfully, but these errors were encountered:
For now, I think we should have everything installed in the patchkit subdir. I realize this leads to a lot of duplication, but I feel we should avoid building any sort of dependency resolution past what we do with install-root.
Basically that's what I was also thinking. As soon as we add that, we could also use a full blown package manager...
Since we have only one python virtualenv it's hard to isolate everything. If we want to use patchkit from within the virtualenv, we also somehow teach the whole virtualenv on how to load the libs. This could break things. I'm pretty sure we pull capstone in at some point via pip. I can see the appeal of static linking now...
I'll try to get it working as subdir-contained as possible.
https://github.com/lunixbochs/patchkit
Problem is it depends on the keystone, capstone, unicorn triad all from git. Should we install those generically and set LD_LIBRARY_PATH so that all other tools can use it, or keep it just to the patchkit subdir?
The text was updated successfully, but these errors were encountered: