I'm building some generated code that creates insanely long names that tripped
the 260 character limit on Windows. I attempted to specify paths using the
\\?\ prefix
(https://msdn.microsoft.com/en-us/library/aa365247(VS.85).aspx#maxpath ) and it
worked on clean builds, but causes various tools
Are libraries built with MinGW-W64 distributions using different configurations
for exceptions (sjlj vs seh) and threads (win32 vs posix) compatible? I've had
success using libraries across different versions of MinGW-W64 so long as I've
stuck with sjlj exceptions and win32 threads. I'm using
I also had problems with GetLastError when I attempted to use a build of
mingw-w32 configured with pthreads:
http://www.mail-archive.com/mingw-w64-public@lists.sourceforge.net/msg04441.html
-Original Message-
From: Ozkan Sezer [mailto:seze...@gmail.com]
Sent: Friday, May 04, 2012 10:30
odes out-side this range, then you need to call explicit TerminateProcess.
Regards,
Kai
2012/3/18 Davidson, Josh :
> I installed Ruben's latest win32 build of mingw-w32 this afternoon and
> immediately ran it runtime issues with third party libraries (one of which is
> boost) that
I installed Ruben's latest win32 build of mingw-w32 this afternoon and
immediately ran it runtime issues with third party libraries (one of which is
boost) that I'm using in my application. After some analysis, the root of the
issue is that the Windows's system error code is cleared upon a func
Is there something that can be configured to change how gcc reports its search
path? I've used different builds of MinGW-W64 and some end up with at least
one standard header path that is completely forward slashes and some end up
with only paths that have at least one backslash. Usually, for
"The procedure entry point vsnprintf could not be located in the dynamic link
library msvcrt.dll"
I know this error has been posted to the mailing list before, but I'm wondering
if there is any way of working around it in binary distributions. I'm using
the latest automated build (mingw-w32-b
