User forums > General (but related to Code::Blocks)
TDM-GCC 4.5 series (Latest: 4.5.2 - 2011-03-27)
TDragon:
--- Quote from: Xaviou on April 04, 2011, 03:15:08 pm ---Can you confirm that 32-bits libs build with the 32/64-bits edition are compatibles with the 32-bits only edition ?
--- End quote ---
Yes. But you're responsible for knowing the ABI of any languages and libraries you try to use in this manner, so please don't post any questions or bug reports when you run into problems when doing this.
--- Quote ---I've tried with the 2.8.12, and encountered problems :
...
If UNICODE=1, all works fine.
Is there something I missed, or is this confirmed ?
--- End quote ---
I haven't tried with 2.8.12.
Xaviou:
Hi
--- Quote from: TDragon on April 07, 2011, 03:38:02 am ---
--- Quote from: Xaviou on April 04, 2011, 03:15:08 pm ---Can you confirm that 32-bits libs build with the 32/64-bits edition are compatibles with the 32-bits only edition ?
--- End quote ---
Yes. But you're responsible for knowing the ABI of any languages and libraries you try to use in this manner, so please don't post any questions or bug reports when you run into problems when doing this.
--- End quote ---
Of course. Thanks for the response.
--- Quote from: TDragon on April 07, 2011, 03:38:02 am ---
--- Quote ---I've tried with the 2.8.12, and encountered problems :
...
If UNICODE=1, all works fine.
Is there something I missed, or is this confirmed ?
--- End quote ---
I haven't tried with 2.8.12.
--- End quote ---
Resolved the problem with UNICODE=0 by adding a #include <direct.h> line in src/common/filefn.cpp and src/common/debugrpt.cpp (thank you reckless for helping me by PM).
So I now can confirm that wxWidgets-2.8.12 can succesfully be build with TDM-GCC 4.5.2 with all classics configurations (I've tried all the 16 differents combinations) :
* Release / Debug
* Ansi / Unicode
* Static / Dynamic
* Multilib / Monolithic
Thanks again to all
Regards
Xav'
stahta01:
I was compiling code from http://cboard.cprogramming.com/cplusplus-programming/139494-getconsolescreenbufferinfoex-function.html#post1039300
And, I found,what I think are, a few typos in w64 headers.
Two in file wincrypt.h.
The structure define of CertSelectCertificateChains
Had "cCriteria DWORD," instead of "DWORD cCriteria,"
The structure define of CryptExportPublicKeyInfoFromBCryptKeyHandle
Had "void pvAuxInfo," instead of what I think was meant of "void* pvAuxInfo,"
One in file objbase.h
The prototype of CoGetApartmentType
Had something else instead of "HRESULT WINAPI CoGetApartmentType("
NOTE: I am just a C Programmer; So, you need to verify these are typos.
Tim S.
xunxun:
--- Quote from: stahta01 on July 15, 2011, 03:15:29 am ---I was compiling code from http://cboard.cprogramming.com/cplusplus-programming/139494-getconsolescreenbufferinfoex-function.html#post1039300
And, I found,what I think are, a few typos in w64 headers.
Two in file wincrypt.h.
The structure define of CertSelectCertificateChains
Had "cCriteria DWORD," instead of "DWORD cCriteria,"
The structure define of CryptExportPublicKeyInfoFromBCryptKeyHandle
Had "void pvAuxInfo," instead of what I think was meant of "void* pvAuxInfo,"
One in file objbase.h
The prototype of CoGetApartmentType
Had something else instead of "HRESULT WINAPI CoGetApartmentType("
NOTE: I am just a C Programmer; So, you need to verify these are typos.
Tim S.
--- End quote ---
You can use latest MinGW64 svn.
These have been fixed.
TDragon:
Perhaps I'll create a new mingw64-runtime package in the near future.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version