Op 15 jan. 2013 23:21 schreef "Peter Kümmel" het
volgende:
>
> I've backported the seh patch to GCC 4.7.2 (all but the changelogs, then
it is a plain cherry-pick):
>
>
https://github.com/syntheticpp/MinGW-w64-build-scripts/commit/32b35ca7ede4c7b318eacea4cb22ce75353edf7c
>
> when configuring --disa
I followed the gcc manual which states that to generate .as files you simply
use gcc -o
but this does NOT work.
when I generate map files, it does generate a .as file
I would like mine with object code...
so I can do some proper debugging based on microsoft crashdumps and the offset
that gives.
On 15 Jan 2013, at 20:24, Ruben Van Boxem wrote:
> As per request of Kai, I have built some small update packages for
> trunk
> MinGW-w64 dated 2013-01-15. It should contain changes useful to Clang
> developers and its TLS support.
Wow, that was quick – thanks a lot, this should make it much easi
I've backported the seh patch to GCC 4.7.2 (all but the changelogs, then it is
a plain cherry-pick):
https://github.com/syntheticpp/MinGW-w64-build-scripts/commit/32b35ca7ede4c7b318eacea4cb22ce75353edf7c
when configuring --disable-dw2-exceptions is needed.
Here
https://github.com/sy
Hi,
As per request of Kai, I have built some small update packages for trunk
MinGW-w64 dated 2013-01-15. It should contain changes useful to Clang
developers and its TLS support.
You can find them at:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Build
Humm, some how I felt that there was something very wrong in my installation.
All I want from the compiler is to debug using 32-bit, and then create a final
built in 64-bit. I not interested in cross compiling, it is just that I want to
deploy under 64-bit Windows 7/8.
Please, could you tell me
2013/1/15 Arbol One
> I hope someone is willing to reply to my question, even though they
> sound not very smart, the truth is that I am trying to understand the
> different aspects of MinGW64, I am really confused about how it works.
>
> Thanks in advance
>
> *From:* Arbol One
> *Sent:* Tues
I hope someone is willing to reply to my question, even though they sound not
very smart, the truth is that I am trying to understand the different aspects
of MinGW64, I am really confused about how it works.
Thanks in advance
From: Arbol One
Sent: Tuesday, January 15, 2013 9:25 AM
To: mingw-w
D:\MinGW64
+bin
-i686-w64-mingw32-g++.exe
+i686-w64-mingw32
+bin
-g++.exe
What is the difference between './bin/i686-w64-mingw32-g++.exe' and
'./i686-w64-mingw32/bin/g++.exe'? What are they used for?
TIA
From: Ruben Van Boxem
Sent: Tuesday, January 15, 2013 9:13
Arbol,
Additional to Ruben's information:
Previously, I've shared mingw configuration web site which is:
http://ingar.satgnu.net/devenv/mingw32/base.html
I thought that configuration is easy and it is easy to switch between
specific toolchains with one command.
Regards
2013/1/15 Arbol One
> In the‘/MinGW64’ folder I have ‘./lib’, ‘/bin’ and ‘./include’
> subdirectories, am I to assume that this are the 32-bit files while their
> 64-bit counterparts are in the ‘./i686-w64-mingw32’ directory?
>
No. Depending on what exactly you downloaded (filename of the fi
In the‘/MinGW64’ folder I have ‘./lib’, ‘/bin’ and ‘./include’
subdirectories, am I to assume that this are the 32-bit files while their
64-bit counterparts are in the ‘./i686-w64-mingw32’ directory?
TIA
From: Ruben Van Boxem
Sent: Tuesday, January 15, 2013 7:18 AM
To: mingw-w64-public@lists
On Mon, Jan 14, 2013 at 4:39 AM, Алексей Павлов wrote:
> Hey!
> Maybe fork new Cygwin to MSYS2 is the best solution? I am interesting in it
> because MSYS is very old and porting new software for it is very difficult.
> I can help you any way I can. I have Cygwin git repo on
> https://github.com/Al
On Mon, Jan 14, 2013 at 10:16 AM, JonY wrote:
>
> MSYS is pretty bad at path translation, it was what drove me to Cygwin
> in the first place. Perhaps some setting on how aggressive it scans and
> assumes a string as a path is a good idea.
>
> gcc -c abc.c -Dfoo="/bar1/bar2" <- is this a path to t
2013/1/15 Arbol One
> Hello there!
> I just downloaded and unpacked mingw-w64-v1.0.7. in my D: directory, what
> else do I have to do now? is there a tutorial explaining what has to be
> added to the path and what is the toolchain for 32bit or 64bit apps?
>
Hi,
you downloaded the MinGW-w64 ru
15 matches
Mail list logo
