Fix Windows Build Issue by Splitting Taskify into OS-Specific Files #48
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the build issue on Windows caused by a Linux-only syscall in tasker.go.
Windows doesn’t support that syscall, so I adjusted the approach by creating an OS-specific setup for the
Taskify
function.Split
tasker.go
by OStasker.go
: Keeps the core tasker functionality, minus theTaskify
function.tasker_windows.go
: Adds a Windows-specificTaskify
function usingCREATE_NEW_PROCESS_GROUP
to handle process group creation.tasker_other.go
: Retains the originalTaskify
function for Linux and other Unix-like systems.This way, the build works perfectly on both Windows and Unix-based OS.
Closes #47