> Use MSVCR100, you don't need to deal with manifests there, MS finally
> dropped it.
Phew! Very good news. i will keep that in mind for my own projects,
as i would like to avoid making Qt IFW change to their project files.
Thanks JonY! Yet another good piece information :)
Pierre.
--
On 5/16/2012 02:54, Kai Tietz wrote:
> 2012/5/15 MARTIN Pierre :
>> Kai,
>>
>>> Well, that isn't surprising, as VC doesn't use msvcrt.dll from OS. It
>>> provides its own msvcr??.dll version by of course contains this
>>> symbol.
>> Understood.
>>
>>> You can build your application with gcc also f
>> I apologize for my two cents, but tell me please, what 'Qt IFW' the project
>> is?
> It is a very interesting project (Qt IFW stands for Installer Framweork). i'm
> able
> to build installer that can check for updates online against XML files that
> you
> craft with your different component i
> I apologize for my two cents, but tell me please, what 'Qt IFW' the project
> is?
It is a very interesting project (Qt IFW stands for Installer Framweork). i'm
able
to build installer that can check for updates online against XML files that you
craft with your different component information.
2012/5/16 MARTIN Pierre:
> ... binaries generated by the Qt IFW project
I apologize for my two cents, but tell me please, what 'Qt IFW' the project is?
Thanks!
--
Regards,
niXman
___
my MinGW builds: http://sourceforge.net/projects/mingwbuilds/
---
Dear Kai, Ozkan, and those reading regarding this msvcrt problem,
As i was investigating more and more about the implications of
tweaking the specs of GCC and then having to embed a manifest
into the binaries generated by the Qt IFW project, i finally choosed
to count the functions that were not p
2012/5/15 MARTIN Pierre :
> Dear list readers,
>
> Related to the msvcrXX.dll problem i have, i'm trying to understand
> how to tell my toolchan that i'll be willing to use msvcr80.
> So i found this page: http://www.mingw.org/wiki/SpecsFileHOWTO
> wich is talking about modifying the specs of gcc.
2012/5/15 MARTIN Pierre :
> Kai,
>
>> Well, that isn't surprising, as VC doesn't use msvcrt.dll from OS. It
>> provides its own msvcr??.dll version by of course contains this
>> symbol.
> Understood.
>
>> You can build your application with gcc also for different
>> runtime-library, but you have t
Dear list readers,
Related to the msvcrXX.dll problem i have, i'm trying to understand
how to tell my toolchan that i'll be willing to use msvcr80.
So i found this page: http://www.mingw.org/wiki/SpecsFileHOWTO
wich is talking about modifying the specs of gcc.
However, something is unclear and re
Kai,
> Well, that isn't surprising, as VC doesn't use msvcrt.dll from OS. It
> provides its own msvcr??.dll version by of course contains this
> symbol.
Understood.
> You can build your application with gcc also for different
> runtime-library, but you have to specify it manually. Also be aware
2012/5/15 MARTIN Pierre :
> Hi Kai,
>
>> This symbol isn't present for older msvcrt.dll versions. Means this
>> issue can happen on OS versions of Windows, where the msvcrt.dll
>> doesn't provide this export. What OS you were actual here using?
> Hm. This would make sense but note the following:
On 5/15/12, MARTIN Pierre wrote:
> Hi Kai,
>
>> This symbol isn't present for older msvcrt.dll versions. Means this
>> issue can happen on OS versions of Windows, where the msvcrt.dll
>> doesn't provide this export. What OS you were actual here using?
> Hm. This would make sense but note the fol
Hi Kai,
> This symbol isn't present for older msvcrt.dll versions. Means this
> issue can happen on OS versions of Windows, where the msvcrt.dll
> doesn't provide this export. What OS you were actual here using?
Hm. This would make sense but note the following: when compiling
the same program wi
2012/5/15 MARTIN Pierre :
> Hello list readers,
>
> i have successfully managed to compile Qt IFW with MinGW-w64.
> i will submit the set of patches to the maintainers, as they requested.
> However, once compiled, i have an error when starting any of the
> generated binary:
> "The procedure entry p
Hello list readers,
i have successfully managed to compile Qt IFW with MinGW-w64.
i will submit the set of patches to the maintainers, as they requested.
However, once compiled, i have an error when starting any of the
generated binary:
"The procedure entry point _wsopen_s could not be located in
15 matches
Mail list logo
