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
Make helpers package into its own go module #243
Comments
Hi, it would also be nice if libbpfgo could be decoupled from it dependency wise as well, otherwise if I try to use it for writing a tracee signature for example I get this error:
This would be useful because then you could use the direct argument values defined in the argument parsers instead of relying on argument parsing before signatures (for exmaple use the |
@NDStrahilevitz Do you mean to say you think helpers shouldn't import libbpfgo? |
Yes, otherwise you can't really use the helpers independently. |
@NDStrahilevitz Where do you get the above error? When building or running |
I made a new go signature using PR #2220 in tracee.
And I got the errors i've written above when compiling to a |
Can you provide the command you use to compile? @NDStrahilevitz |
This was standard signature compilation in tracee so just
|
@NDStrahilevitz is this still relevant? Perhaps correlated to #297? |
If consumers of the helpers package want to import a new version without upgrading libbpfgo, it becomes impossible because it's a single module.
The text was updated successfully, but these errors were encountered: