Skip to main content
added 111 characters in body
Source Link
Tom Yan
  • 10k
  • 2
  • 18
  • 37

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.


w64devkit and WinLibs are alternatives that might interest you. (Not sure if you'll get any cat with the latter though.)


GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. (Well, there are different implementations of cat I suppose; for example you also get a cat from busybox.) I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.

GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. (Well, there are different implementations of cat I suppose; for example you also get a cat from busybox.) I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.


w64devkit and WinLibs are alternatives that might interest you. (Not sure if you'll get any cat with the latter though.)


GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. (Well, there are different implementations of cat I suppose; for example you also get a cat from busybox.) I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

added 111 characters in body
Source Link
Tom Yan
  • 10k
  • 2
  • 18
  • 37

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.

GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. (Well, there are different implementations of cat I suppose; for example you also get a cat from busybox.) I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.

GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.

GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. (Well, there are different implementations of cat I suppose; for example you also get a cat from busybox.) I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)

Source Link
Tom Yan
  • 10k
  • 2
  • 18
  • 37

The fact that "your project" uses cat in its build process indicate it's likely a project that targeted (originally, at least) Linux (well, or other UNIX-like OS).

In that case (or perhaps even, in any case that isn't a VS project?), you probably need a full toolchain et. al. (well, e.g. cat) anyway, and msys2 is probably one of the choices you want to consider. It provides different shells that are set up to allow the building of either native Windows (mingw) builds or msys2 builds (which rely on a POSIX compatibility layer / library that msys2 provides) of a program.

Note that whether you can build your the program as the former depends on the portability of the program itself.

GNU Make is really just a program that processes Makefiles. Whether it is sufficient for your "project" depends on what exactly will be run (directly or indirectly) as the Makefile instructed.

cat is part of GNU coreutils. I'm not sure if it is possible to build native build of it for Windows anymore. Apparently there's an ancient port though, which you can get with chocolatey as well. (Another option could be this.)