[Mingw-w64-public] differences/similarities between .a and .lib for 32-bit and 64-bit

Hi all, I've searched high and low through the internets to understand MSVC static libs vs MinGW static libs. I couldn't find a satisfactory answer, and got quite confused in the process. As I understand, both are ar archives made up of COFF object files. Correct? C 32 bit libs probably mostly

Re: [Mingw-w64-public] [Project News|New Builds]

niXman 2017-08-15 10:23: Adrien Nader 2017-08-15 10:16: Have you checked your emails, including the spam folder? Yes. ping? -- Regards, niXman ___ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows:

Re: [Mingw-w64-public] [PATCH 00/12] Def file cleanups and merging

LGTM. On Tue, 15 Aug 2017, at 10:36, Martin Storsjö wrote: > Hi, > > While trying to share def files between different architectures, I've > first cleaned them up, getting rid of unnecessary ones, and then started > off by sharing ones where it can easily be done without too much manual >

[Mingw-w64-public] [PATCH 12/12] crt: Share defs where libarm32 has got a superset of the functions in lib64

In these cases, use the libarm32 version for both. None of the differences should be architecture specific. Signed-off-by: Martin Storsjö --- mingw-w64-crt/Makefile.am | 4 +- mingw-w64-crt/{libarm32 => lib-common}/atl.def | 0

[Mingw-w64-public] [PATCH 06/12] crt: Remove even more def files that only contain DLL hooks or similar

These defs only export DLL hooks, and one of the following entry points: - GetProxyDllInfo - GetResourceString - InitHelperDll - ServiceEntry - ServiceMain Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib64/Makefile.am | 23 ---

[Mingw-w64-public] [PATCH 02/12] crt: Remove the executable bit from def files

Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib-common/devrtl.def | 0 mingw-w64-crt/lib32/user32.def | 0 mingw-w64-crt/lib64/devobj.def | 0 3 files changed, 0 insertions(+), 0 deletions(-) mode change 100755 => 100644 mingw-w64-crt/lib-common/devrtl.def mode

[Mingw-w64-public] [PATCH 09/12] crt: Share def files that only differ in unnamed ordinals between lib64 and libarm32

Signed-off-by: Martin Storsjö --- mingw-w64-crt/Makefile.am | 6 +- mingw-w64-crt/{lib64 => lib-common}/comdlg32.def | 0 mingw-w64-crt/{lib64 => lib-common}/gdiplus.def | 0 mingw-w64-crt/{lib64 => lib-common}/rpcss.def | 0

[Mingw-w64-public] [PATCH 05/12] crt: Remove printer monitor DLL def files

Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib-common/inetpp.def | 9 - mingw-w64-crt/lib-common/inetppui.def | 9 - mingw-w64-crt/lib64/Makefile.am | 13 - mingw-w64-crt/lib64/cnbjmon.def | 9 -

[Mingw-w64-public] [PATCH 03/12] crt: Remove def files for DLLs with code page translations

These aren't DLL files that one links to directly. Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib-common/c_is2022.def | 9 - mingw-w64-crt/lib-common/c_iscii.def | 9 - mingw-w64-crt/lib64/Makefile.am | 3 --- mingw-w64-crt/lib64/c_g18030.def

[Mingw-w64-public] [PATCH 10/12] crt: Share defs that only differ in dll entry points between lib64 and libarm32

Signed-off-by: Martin Storsjö --- mingw-w64-crt/{lib64 => lib-common}/acledit.def | 0 mingw-w64-crt/{lib64 => lib-common}/activeds.def | 0 mingw-w64-crt/{lib64 => lib-common}/appmgr.def | 0 mingw-w64-crt/{lib64 => lib-common}/asycfilt.def | 0 mingw-w64-crt/{lib64 =>

[Mingw-w64-public] [PATCH 01/12] crt: Convert def files from dos newline to unix newlines

Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib32/d3dcompiler_47.def | 72 +- mingw-w64-crt/lib64/d3dcompiler_47.def | 72 +- 2 files changed, 72 insertions(+), 72 deletions(-) diff --git

[Mingw-w64-public] [PATCH 07/12] crt: Remove defs that only contain C++ functions

Since the mingw C++ runtime isn't compatible with the MSVC C++ runtime (and uses a completely different name mangling), these def files aren't of much use. Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib32/Makefile.am |1 -

[Mingw-w64-public] [PATCH 00/12] Def file cleanups and merging

Hi, While trying to share def files between different architectures, I've first cleaned them up, getting rid of unnecessary ones, and then started off by sharing ones where it can easily be done without too much manual inspection. Patches for sharing def files where manual modifications has to be

[Mingw-w64-public] [PATCH 08/12] crt: Share identical def files between lib64 and libarm32

These were missed before due to the differing line endings. Signed-off-by: Martin Storsjö --- mingw-w64-crt/Makefile.am | 2 +- .../{lib64 => lib-common}/d3dcompiler_47.def | 0 mingw-w64-crt/libarm32/d3dcompiler_47.def | 36

[Mingw-w64-public] [PATCH 11/12] crt: Share defs where lib64 has got a superset of the functions in libarm32

In these cases, use the lib64 version for both. None of the differences should be architecture specific. Signed-off-by: Martin Storsjö --- mingw-w64-crt/{lib64 => lib-common}/dnsapi.def | 0 mingw-w64-crt/{lib64 => lib-common}/dsrole.def | 0 mingw-w64-crt/{lib64 =>

[Mingw-w64-public] [PATCH 04/12] crt: Remove a nonsense def for a modem driver DLL

Signed-off-by: Martin Storsjö --- mingw-w64-crt/lib64/Makefile.am | 1 - mingw-w64-crt/lib64/agrmco64.def | 9 - 2 files changed, 10 deletions(-) delete mode 100644 mingw-w64-crt/lib64/agrmco64.def diff --git a/mingw-w64-crt/lib64/Makefile.am

Re: [Mingw-w64-public] [Project News|New Builds]

Adrien Nader 2017-08-15 10:16: Have you checked your emails, including the spam folder? Yes. -- Regards, niXman ___ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: https://sf.net/p/mingw-w64/

Re: [Mingw-w64-public] [Project News|New Builds]

On 2017/8/15 15:16, Adrien Nader wrote: On Tue, Aug 15, 2017, niXman wrote: Liu Hao 2017-08-15 05:59: When I click the Register button the page reloads and nothing happens thereafter. +1 Have you checked your emails, including the spam folder? Yes. There are no such mails. -- Best

Re: [Mingw-w64-public] [Project News|New Builds]

On Tue, Aug 15, 2017, niXman wrote: > Liu Hao 2017-08-15 05:59: > > >When I click the Register button the page reloads and nothing happens > >thereafter. > > +1 Have you checked your emails, including the spam folder? -- Adrien