-
Notifications
You must be signed in to change notification settings - Fork 29
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
Question: Feature Implementations #6
Comments
As I am not working actively on the project, I cannot say when I will be able to deliver those features. For instance, I give some of my spare time to work on the stream API, which is almost done. |
Hi Hugal31, one final question, by using the bindgen with your crate, does the Yara binary get compiled with my program as a resource to {{ my.exe }}? Or does your crate provide wrappers and I need to have Yara binaries deployed on the target machine? I ask because my needs are to deploy a rust compiled binary {{ my.exe }} that can offer Yara scanning without having to deliver additional payloads. |
Hum, if you look at this line in the yara-sys build.sh ( So, IIRC, if the linker finds only a static library (.a or .lib), it will link statically, and if it finds a shared library (.so or .dll), it will prefer to link dynamically. You can force rustc to link statically by replacing the option in the build.sh by I might add a feature flag to the crate to specify the link type. I hope that respond to your question ! |
Related: #7 |
@Hugal31 If I understand correctly, can we close this one? |
Hi
What is the possible estimate on ur implementation of these features from the REDAME?
Implement the scanner API.
Add process scanning.
The text was updated successfully, but these errors were encountered: