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

docs: DEVELOPER_GUIDE: add instructions for windows 2022. #9522

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

niedbalski
Copy link
Collaborator

This pull request adds new documentation to the DEVELOPER_GUIDE for building and running fluent on Windows Server 2022.

  • Added Windows 2022 setup instructions. step-by-step for setting up the environment to build Fluent Bit on Windows Server 2022, including Visual Studio installation, Flex and Bison setup, and dependency management using vcpkg.
  • Also, I corrected references from Chocolatey to vcpkg for dependency installation, aligning the local build guide with the tools used in CI.

@niedbalski niedbalski self-assigned this Oct 24, 2024
@niedbalski niedbalski marked this pull request as ready for review October 24, 2024 11:16
Copy link
Contributor

@cosmo0920 cosmo0920 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

* Adds Windows 2022 setup instructions. step-by-step for setting up the environment to build Fluent Bit on Windows Server 2022, including Visual Studio installation, Flex and Bison setup, and dependency management using vcpkg.

* Corrected references from Chocolatey to vcpkg for dependency installation, aligning the local build guide with the tools used in CI.

Signed-off-by: Jorge Niedbalski <[email protected]>
@niedbalski niedbalski merged commit 6fccaa2 into master Oct 29, 2024
35 checks passed
@niedbalski niedbalski deleted the docs-windows-2022 branch October 29, 2024 10:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants