Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Helpful "getting started" content to link to, that I wrote

Open
  • Is something wrong?
#379 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
bash, c, cmake, cpp
Domain
documentation

Research direction

Review the MSYS2 homepage and the Stack Overflow answers and repository linked in the issue. Identify an appropriate location for these resources, then add links where they help users get started; done means the selected content is linked from the website and remains relevant to the surrounding guidance.

Written by the indexing model from the issue text.

Description

To help people with a variety of MSYS challenges and getting started, here are some tutorial-like answers and content I've produced that I invite you to link to somewhere on your website:

  1. Installing & setting up MSYS2 from scratch, including adding all 7 profiles to Windows Terminal...so you can build native Windows applications with gcc on Windows.
    1. Part 2, including building, CMake, and Unix sockets on Windows
  2. Detecting your build platform/environment in C and C++ at compile-time in Linux, Windows, GCC, MSYS2, Cygwin, etc.
  3. My repo: full demo of building and running Unix sockets in the MSYS terminl on Windows: https://github.com/ElectricRCAircraftGuy/eRCaGuy_Linux_Windows_CMake_Sockets_MSYS2
  4. How to specify in which of the 7 MSYS2 terminals to run a command in Windows from Bash, Command Prompt, & PowerShell

I'm a Linux user, so thank you so much for finally making Windows development bearable! With MSYS2 I can build and run the same code on Windows, including Unix sockets, as I can on Linux! THANK YOU!

Dominant language
CSS
Stars
3.3k
Forks
446
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from msys2/msys2.github.io

All issues in msys2/msys2.github.io

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.