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

chore!: refine windows platform configuration #76

Merged
merged 3 commits into from
Jun 13, 2024

Conversation

cavivie
Copy link
Collaborator

@cavivie cavivie commented Jun 13, 2024

Closes 75.

@cavivie cavivie marked this pull request as draft June 13, 2024 12:16
@cavivie cavivie requested a review from ssrlive June 13, 2024 12:22
@cavivie cavivie marked this pull request as ready for review June 13, 2024 12:22
@ssrlive ssrlive merged commit 8ec27d1 into tun2proxy:v2 Jun 13, 2024
3 checks passed
@cavivie
Copy link
Collaborator Author

cavivie commented Jun 13, 2024

I don't understand why the .dll ext needs to be removed here?

@ssrlive
Copy link
Member

ssrlive commented Jun 13, 2024

It can be automatically added by the LoadLibraryExW function.

@cavivie
Copy link
Collaborator Author

cavivie commented Jun 13, 2024

In this case, I prefer to say wintun_path here is wintun_file to make it clearer that wintun is just a filename or a filename with an extension, because wintun looks too much like a path due to the function name is called wintun_path, which will lead users to use wintun path(directory). What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Custom loading of wintun.dll should be a feature
2 participants