npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

liam-tools-gcc

v0.0.1

Published

gcc,c,c++

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

liamliuliamliu

Keywords

gcccc++

Readme

readme.md

  • You will probably want to install some tools like the mingw-w64 GCC to start compiling projects. Run the following command: pacman -S --needed base-devel mingw-w64-ucrt-x86_64-toolchain

  • The terminal window will show the output as below. Press 'Enter' to continue:

      resolving dependencies...
  looking for conflicting packages...

  Packages (15) mingw-w64-ucrt-x86_64-binutils-2.41-2
              mingw-w64-ucrt-x86_64-crt-git-11.0.0.r216.gffe883434-1
              mingw-w64-ucrt-x86_64-gcc-libs-13.2.0-2  mingw-w64-ucrt-x86_64-gmp-6.3.0-2
              mingw-w64-ucrt-x86_64-headers-git-11.0.0.r216.gffe883434-1
              mingw-w64-ucrt-x86_64-isl-0.26-1  mingw-w64-ucrt-x86_64-libiconv-1.17-3
              mingw-w64-ucrt-x86_64-libwinpthread-git-11.0.0.r216.gffe883434-1
              mingw-w64-ucrt-x86_64-mpc-1.3.1-2  mingw-w64-ucrt-x86_64-mpfr-4.2.1-2
              mingw-w64-ucrt-x86_64-windows-default-manifest-6.4-4
              mingw-w64-ucrt-x86_64-winpthreads-git-11.0.0.r216.gffe883434-1
              mingw-w64-ucrt-x86_64-zlib-1.3-1  mingw-w64-ucrt-x86_64-zstd-1.5.5-1
              mingw-w64-ucrt-x86_64-gcc-13.2.0-2

  Total Download Size:    49.38 MiB
  Total Installed Size:  418.82 MiB

  :: Proceed with installation? [Y/n]
  [... downloading and installation continues ...]

  • Now you can call gcc to build software for Windows.

gcc --version
gcc.exe (Rev2, Built by MSYS2 project) 13.2.0
  • After installing MSYS2 it will update itself via pacman, see the update guide for more information.

Add the path of your MinGW-w64 bin folder to the Windows PATH environment variable by using the following steps:

In the Windows search bar, type Settings to open your Windows Settings. Search for Edit environment variables for your account. In your User variables, select the Path variable and then select Edit. Select New and add the MinGW-w64 destination folder you recorded during the installation process to the list. If you used the default settings above, then this will be the path: C:\msys64\ucrt64\bin. Select OK, and then select OK again in the Environment Variables window to update the PATH environment variable. You have to reopen any console windows for the updated PATH environment variable to be available.

Check your MinGW installation To check that your MinGW-w64 tools are correctly installed and available, open a new Command Prompt and type:

gcc --version
g++ --version
gdb --version

You should see output that states which versions of GCC, g++ and GDB you have installed. If this is not the case:

  • Make sure your PATH variable entry matches the MinGW-w64 binary location where the toolchain was installed. If the compilers do not exist at that PATH entry, make sure you followed the previous instructions.
  • If gcc has the correct output but not gdb, then you need to install the packages you are missing from the MinGW-w64 toolset.
    • If on compilation you are getting the "The value of miDebuggerPath is invalid." message, one cause can be you are missing the mingw-w64-gdb package.