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.

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

why is the tool using tox internals via include and not the public API? #2826

Closed
zoff99 opened this issue Jan 11, 2025 · 1 comment
Closed
Milestone

Comments

@zoff99
Copy link

zoff99 commented Jan 11, 2025

#include "../toxencryptsave/toxencryptsave.h"

like this the tool can not be used as-is standalone with toxcore installed system wide

@iphydf
Copy link
Member

iphydf commented Jan 11, 2025

It's just like all other tools and things in the testing/ directory, or anything in the toxcore source tree. These are not "toxins", they are testing utilities inside toxcore. Feel free to make a PR into the toxins repo to make this a public tool to be built against a system toxcore.

@iphydf iphydf added this to the v0.2.21 milestone Jan 11, 2025
@iphydf iphydf closed this as not planned Won't fix, can't repro, duplicate, stale Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants