2013/6/5 dw
>
> > When using latest mingw-w64 runtime from trunk for Cygwin I have
> > error: http://pastebin.com/9WVgE1Gu
>
> I would like to experiment with some alternate solutions to what ktietz
> proposed, but I need to be sure I understand what is going wrong.
>
> My attempts to reproduce t
> When using latest mingw-w64 runtime from trunk for Cygwin I have
> error: http://pastebin.com/9WVgE1Gu
I would like to experiment with some alternate solutions to what ktietz
proposed, but I need to be sure I understand what is going wrong.
My attempts to reproduce the problem have not been
You missed the hunk for winnt.h header.
Kai
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of ente
2013/6/4 dw :
>
>>> I think option #3 is that one I prefer too. Just one thing about
>>> SSE-instruction. For 64-bit we can assume that SSE has to be present
>>> in any case. Just for 32-bit we should check in headers for the
>>> __SSE__ macro, and in the intrinsic-function (none-inline) we shou
Oh, I am sorry! I change winnt.h bat forgot to click save button)
It works now Kai!
2013/6/4 Kai Tietz
> You missed the hunk for winnt.h header.
>
> Kai
>
>
> --
> How ServiceNow helps IT people transform IT department
2013/6/4 Kai Tietz
> Hmm, could you try if the following patch solves your problem?
>
> Kai
>
> Index: winnt.h
> ===
> --- winnt.h(Revision 5878)
> +++ winnt.h(Arbeitskopie)
> @@ -1542,10 +1542,10 @@ extern "C" {
> VOID
Hmm, could you try if the following patch solves your problem?
Kai
Index: winnt.h
===
--- winnt.h(Revision 5878)
+++ winnt.h(Arbeitskopie)
@@ -1542,10 +1542,10 @@ extern "C" {
VOID __stosq(PDWORD64 Destination,DWORD64 Va
Le 04/06/2013 13:34, Rafaël Carré a écrit :
> ---
> mingw-w64-crt/Makefile.am | 6 ++-
> mingw-w64-crt/lib32/runtimeobject.def | 25
> mingw-w64-crt/lib64/runtimeobject.def | 29 +
> mingw-w64-headers/include/hstring.h | 61 +++
> min
---
mingw-w64-crt/Makefile.am | 6 ++-
mingw-w64-crt/lib32/runtimeobject.def | 25
mingw-w64-crt/lib64/runtimeobject.def | 29 +
mingw-w64-headers/include/hstring.h | 61 +++
mingw-w64-headers/include/hstring.idl | 27
mi
You can setup wrapper scripts to do this sort of thing. Many projects take
this approach. Personally I prefer doing this and being able to use
multilib toolchains, but each to their own!
Sample contents would be something like:
#!/bin/bash
exec /mingw/bin/windres -F pe-i386 "${@}"
On Tue, Jun
Thanks for adding the hstring.h header. Nevertheless there is still
one nit. In winstring.h you need of course to include now hstring.h
header.
Cheers,
Kai
--
How ServiceNow helps IT people transform IT departments:
1.
Hello,
Le 03/06/2013 16:51, JonY a écrit :> On 6/3/2013 22:18, Rafaël Carré wrote:
>
>> new file mode 100644
>> index 000..c49fc51
>> --- /dev/null
>> +++ b/mingw-w64-crt/lib32/runtimeobject.def
>> @@ -0,0 +1,25 @@
>> +LIBRARY "api-ms-win-core-winrt-string-l1-1-0.dll"
>
>
>> new file mode 1006
2013/6/4 zhangxinghai
> hello
> I find there is no way to control the output file format of windres
> directly when I build wx.
> If I use mingw32-make under cmd,I must manually modify makefile.gcc,add
> rcflags to
> every windres command.
> If I use msys,I also have no way to directly do that
hello
I find there is no way to control the output file format of windres directly
when I build wx.
If I use mingw32-make under cmd,I must manually modify makefile.gcc,add rcflags
to
every windres command.
If I use msys,I also have no way to directly do that using configure,
../../configure -
14 matches
Mail list logo
