AFAIK, ld.gold is designed to output only ELF [1] binaries (and the
specialization is what makes it superior to GNU ld when outputting ELF),
while Windows use PE [2] binaries.
So you cannot.
[1] https://en.wikipedia.org/wiki/Executable_and_Linkable_Format
[2] https://en.wikipedia.org/wiki/Por
Hi,all
My OS is xp sp3
I used the i686-4.9.2-release-posix-dwarf-rt_v4-rev2.7z build from site
http://sourceforge.net/projects/mingw-w64
I write a helloworld.cpp program
#include
#include
int main()
{
int i1=1,i2=2;
int sum = i1 + i2;
printf("%d\n",sum);
return 0;
}
when I use g++ -o hello.exe h
On 05/14/15 16:43, Shaddy Baddah wrote:
> I've thrown a bit out there. So first thing is, it is not a
> bug/incorrect for the two different declarations to be in swprint.inl?
>
> Is the eclipse code wrong to use the first form, over the second? The
> code is C and not C++.
No, it's not a bug. Hist
On Fri, 2015-05-15 at 00:43 +1000, Shaddy Baddah wrote:
> Hi,
>
> I've been trying to use mingw-64 to build the eclipse native launcher
> (.exe).
>
> I encountered an issue around the indirect (via preprocessor defines) of
> swprintf.
>
> The eclipse code usage of swprintf suggested that the dec
Hi,
I've been trying to use mingw-64 to build the eclipse native launcher
(.exe).
I encountered an issue around the indirect (via preprocessor defines) of
swprintf.
The eclipse code usage of swprintf suggested that the declaration should
match this (from
https://msdn.microsoft.com/en-us/library
On 14/05/15 08:03, Steve Lhomme wrote:
> In general I find the whole process awkward. Wine should only add IDL
> definitions when the classes are supported.
That's not true, it's fine to add declarations for not supported APIs to
Wine. It's just the first step to support them.
Jacek
---
