SYS2 for the two targets. You have
shortcuts that add /mingw64/bin or /mingw32/bin to PATH automatically, or
you can do it manually when you need a quick switch.
Don't underestimate MSYS2, it's quite brilliant in its relative simplicity
;-)
Cheers,
Ruben
>
>
> -------
__
> From: Baruch Burstein
>To: mingw-w64-public@lists.sourceforge.net
>Sent: Tuesday, July 22, 2014 5:31 AM
>Subject: [Mingw-w64-public] MSYS2 issues
>
>
>
>Hi,
>
>
>I (think I) found a bug in msys2. Here is a simple demo case:
>
>
>main.c:
Yes, the shell that is run is the bash shell for MSYS2 make and
cmd.exe for mingw32-make, and there are some other differences about
the handling of 'special' characters. By default you should use MSYS2
make, unless you have a compelling reason not to.
-
On Tue, Jul 22, 2014 at 3:36 PM, Ray Donnelly
wrote:
> No, you didn't find any bug in MSYS2.
>
> If you want MSYS2 path translation to happen then use an MSYS2
> program, i.e. MSYS2 make, not mingw32-make.
>
Oh, OK, sorry. I thought that any program run from within msys got
automatic path transl
No, you didn't find any bug in MSYS2.
If you want MSYS2 path translation to happen then use an MSYS2
program, i.e. MSYS2 make, not mingw32-make.
--
Want fast and easy access to all the code in your enterprise? Index and
s
Hi,
I (think I) found a bug in msys2. Here is a simple demo case:
main.c:
int main() { return 42; }
Makefile:
CC = gcc
CC2 = $(shell which $(CC))
out_1: clean main.c
$(CC) main.c -o /home/username/out.exe
out_2: clean main.c
$(CC) /home/username/main.c -o out.exe
out_3: clean main.c
$(CC) main.c
