Re: [Mingw-w64-public] [patch] Prefer to use local headers over installed headers

2013-03-15 Thread NightStrike
On Fri, Mar 15, 2013 at 3:24 PM, John E. / TDM wrote: > On 3/15/2013 8:14 AM, NightStrike wrote: >> On Fri, Mar 15, 2013 at 12:55 AM, John E. / TDM wrote: >>> The headers seem to get built along with all the other subtrees... ? >> Curious... when configuring the crt, which headers is it checking

Re: [Mingw-w64-public] [patch] Prefer to use local headers over installed headers

2013-03-15 Thread John E. / TDM
On 3/15/2013 8:14 AM, NightStrike wrote: > On Fri, Mar 15, 2013 at 12:55 AM, John E. / TDM wrote: >> The headers seem to get built along with all the other subtrees... ? > Curious... when configuring the crt, which headers is it checking for > _mingw_mac.h? The soon-to-be-built ones, or the > alr

Re: [Mingw-w64-public] [patch] Prefer to use local headers over installed headers

2013-03-15 Thread JonY
On 3/15/2013 22:14, NightStrike wrote: > Curious... when configuring the crt, which headers is it checking for > _mingw_mac.h? The soon-to-be-built ones, or the > already-installed-as-part-of-the-toolchain ones? Similarly, which is > it compiling against? > It is a sanity check, to make sure we

Re: [Mingw-w64-public] [patch] Prefer to use local headers over installed headers

2013-03-15 Thread Corinna Vinschen
On Mar 15 06:09, JonY wrote: > On 3/14/2013 23:52, Corinna Vinschen wrote: > > > > What two build systems? It's a fairly simple patch which allows the > > normal user of mingw64 to build the entire source tree in a single > > `configure; make; make install', nothing more, nothing less. I don't >

Re: [Mingw-w64-public] [patch] Prefer to use local headers over installed headers

2013-03-15 Thread NightStrike
On Fri, Mar 15, 2013 at 12:55 AM, John E. / TDM wrote: > On 3/14/2013 8:54 PM, NightStrike wrote: >> On Thu, Mar 14, 2013 at 4:22 PM, John E. / TDM wrote: >>> $(RUNTIME_SRC)/configure --build=x86_64-w64-mingw32 --enable-lib32 >>> --enable-sdk=all --with-libraries=libmangle --with-tools=all >>> --

Re: [Mingw-w64-public] Using Google to search MinGW-w64-public archives

2013-03-15 Thread Earnie Boyd
On Fri, Mar 15, 2013 at 12:28 AM, Mook wrote: > On 3/14/2013 8:48 AM, Earnie Boyd wrote: >> I've noticed some saying the SF archives search blows, here is an >> alternative using Google: >> >> "mingw-w64-public"+SearchItem+SearchItemN >> site:sourceforge.net/mailarchive/forum.php >> > gmane also ha

Re: [Mingw-w64-public] Using Python and Mingw64

2013-03-15 Thread Václav Šmilauer
One other thing , i configure Sip with /python configure.py DEFINES+=MS_WIN64 -p win32-g++/ Does it change something? For me it works without MS_WIN64. (I am glad I compiled everything I needed, only occasionally rebooting to windows for a build; so I don't feel like experimenting with such

Re: [Mingw-w64-public] Using Python and Mingw64

2013-03-15 Thread Václav Šmilauer
ok, i just want to confirm. I patched the cygwinccompiler.py file to /return ['msvcr90'] /(line 77) when /get_msvcr()/ is called. So if a build the Sip.pyd with mingw, and inspect the result in DendencyWalker I should see that Sip.pyd depended on MSVCR90 and not MSVCRTL ? Because after the p

Re: [Mingw-w64-public] Using Python and Mingw64

2013-03-15 Thread Alexpux
I think it would be great if patches will be merged in Python tree and we can build Python with mingw without this big list of patches. I can help with splitting too some later when finish some work on MSYS2. 15.03.2013, в 11:37, Ray Donnelly написал(а): > Hi Ruben. > > It would be great to

Re: [Mingw-w64-public] Using Python and Mingw64

2013-03-15 Thread Ray Donnelly
Hi Ruben. It would be great to have recruit you to the cause to get these merged. My experience in that regard has been a bit frustrating. I think the patches are split up reasonably, except for the huge ones from Roumen Petrov. Due to Alexey's mingwbuilds efforts, Qt 5.0.1 use this Python for the