The mingw-builds distro uses relative paths had worked well in any install
location for the past two years at least.
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/
It also includes the absolute path of the build original location b
On 6/20/2015 8:25 PM, Edward Diener wrote:
> Thanks ! I will look at your toolchains. I assume if all paths are
> relative there is no need for any installation to go into or have a
> symbolic link from c:\mingw.
Correct.
> Any timeframe for a gcc 5.1 release ? I noticed the latest mingw-64
> ins
On 6/20/2015 9:38 PM, John E. / TDM wrote:
> On 6/20/2015 7:30 PM, Edward Diener wrote:
>> But you are creating a product for Windows in which the entire product,
>> including the gcc compiler, standard C library, standard C++ library,
>> and whatever other tools are entailed in a mingw-64 release,
On 6/20/2015 7:30 PM, Edward Diener wrote:
> But you are creating a product for Windows in which the entire product,
> including the gcc compiler, standard C library, standard C++ library,
> and whatever other tools are entailed in a mingw-64 release, are all
> part of any mingw-64 distribution. Th
On 6/20/2015 7:52 PM, JonY wrote:
> On 6/21/2015 05:08, LRN wrote:
>> On 20.06.2015 19:21, Edward Diener wrote:
>>> On 6/20/2015 10:50 AM, LRN wrote:
On 20.06.2015 17:43, Edward Diener wrote:
> Why does mingw-64, or the original mingw for that matter, consistently
> hardcode include an
On 6/20/2015 5:08 PM, LRN wrote:
> On 20.06.2015 19:21, Edward Diener wrote:
>> On 6/20/2015 10:50 AM, LRN wrote:
>>> On 20.06.2015 17:43, Edward Diener wrote:
Why does mingw-64, or the original mingw for that matter, consistently
hardcode include and lib search paths in their build for c
On 6/21/2015 05:08, LRN wrote:
> On 20.06.2015 19:21, Edward Diener wrote:
>> On 6/20/2015 10:50 AM, LRN wrote:
>>> On 20.06.2015 17:43, Edward Diener wrote:
Why does mingw-64, or the original mingw for that matter, consistently
hardcode include and lib search paths in their build for c:\
On 20.06.2015 19:21, Edward Diener wrote:
> On 6/20/2015 10:50 AM, LRN wrote:
>> On 20.06.2015 17:43, Edward Diener wrote:
>>> Why does mingw-64, or the original mingw for that matter, consistently
>>> hardcode include and lib search paths in their build for c:\mingw
>>> instead of searching for in
Hi Mattias!
On Sat, Jun 20, 2015 at 4:32 AM, Mattias Engdegård wrote:
> 19 jun 2015 kl. 23.12 skrev Alexandre Pereira Nunes
> :
>
>> I came across this: https://sourceforge.net/p/mingw-w64/bugs/344/
>>
>> Does anyone knows if that's still the case?
>
> Yes. There is a patch, but it has not been
On 6/20/2015 10:50 AM, LRN wrote:
> On 20.06.2015 17:43, Edward Diener wrote:
>> Why does mingw-64, or the original mingw for that matter, consistently
>> hardcode include and lib search paths in their build for c:\mingw
>> instead of searching for include files and libraries relative to its
>> ins
On 20.06.2015 17:43, Edward Diener wrote:
> Why does mingw-64, or the original mingw for that matter, consistently
> hardcode include and lib search paths in their build for c:\mingw
> instead of searching for include files and libraries relative to its
> installation structure ?
This is a side
Why does mingw-64, or the original mingw for that matter, consistently
hardcode include and lib search paths in their build for c:\mingw
instead of searching for include files and libraries relative to its
installation structure ?
Hardcoding absolute paths makes it so much harder running differ
This is the likely the result of out of memory, maybe the app is leaking
memory.
Watch its memory usage over the days and see if it's growing.
2015-06-20 16:43 GMT+03:00 Ragnar Rüütel :
> Dear all,
>
> I have a small multithreaded application which keeps crashing after
> working for 7-10 days and
A bad alloc could mean your process got out of virtual address space. The
most likely cause would be a memory leak. Make 100% sure you're freeing
every allocated resource or use a memory leak tool to diagnose it. Perhaps
you have threads leaving that aren't deallocating everything. For instance
don
Dear all,
I have a small multithreaded application which keeps crashing after working
for 7-10 days and I'm hoping some of You might be able to identity
my misdoing and provide some suggestions how to overcome this problem.
The application is cross-compiled (under Linux for Win64) with:
Gcc versi
19 jun 2015 kl. 23.12 skrev Alexandre Pereira Nunes :
> I came across this: https://sourceforge.net/p/mingw-w64/bugs/344/
>
> Does anyone knows if that's still the case?
Yes. There is a patch, but it has not been cleared for release yet. It may take
a few weeks more, given that people are on ho
16 matches
Mail list logo
