Dear list,
I am struggling a little with a recent revision of the MinGW-w64 runtime. I use
the latest snapshot from openSuse to install my cross-compiler tool chain. I
used Qt4 in the past and want to migrate to Qt5. During this process I
experience the following issue:
In my project I link ag
Interesting. Well that is even more good news if the issue is already fixed in
trunk!
Best regards!
Sebastian
> From: LRN
> Subject: Re: [Mingw-w64-public] Undefined symbol:
> __mingw_set_output_format using MinGW-w64 3.1.0
> To: mingw-w64-public@lists.sourceforge.net
>
>
> Glad to hear
regards
Sebastian
On 19 Feb 2014, at 17:05, Sebastian Wolff wrote:
> Dear list,
>
> today I upgraded from a SVN revision from March 2013 of the MinGW-w64 runtime
> to version 3.1.0. I use the open build service provided by the openSUSE
> community to install my cross compiler fram
Dear list,
today I upgraded from a SVN revision from March 2013 of the MinGW-w64 runtime
to version 3.1.0. I use the open build service provided by the openSUSE
community to install my cross compiler framework (based on openSuse Linux
12.2). GCC version is 4.8.2. Target system is x64.
Since
;
> Le 08/04/2013 11:32, Sebastian Wolff a écrit :
>> Dear list,
>>
>> a while ago you helped me linking against msvcr90.dll using mingw-w64
>> targeting Win64, see
>> http://sourceforge.net/mailarchive/message.php?msg_id=30556805
>>
>> In my toolch
Dear list,
a while ago you helped me linking against msvcr90.dll using mingw-w64 targeting
Win64, see http://sourceforge.net/mailarchive/message.php?msg_id=30556805
In my toolchain I use the MinGW-w64 distribution of openSuse. I reinstalled the
sources of the MinGW-w64 runtime, patched the mak
, any thrown exception was
leading to an abnormal program termination because any try catch(…) block was
ignored.
Best regards
Sebastian
On Mar 4, 2013, at 4:42 PM, Sebastian Wolff wrote:
> Hello Kai,
>
>
>> The file can be generated via '-dlltool moldname-msvcrt
Hello Kai,
> The file can be generated via '-dlltool moldname-msvcrt.def -U
> --dllname msvcr90.dll'
Wonderful !!! That did the trick.
I did not manage to use this command directly ( it did not do anything on my
machine), but I finally was able to build liboldname90 and the application
wo
Hello Earnie,
>>
>
> Yes, http://msdn.microsoft.com/en-us/library/ms235460.aspx.
>
The same source also states that the option /MD lets the application chose one
runtime (although multiple may be referenced by the DLLs). This is the case,
when I compile my test program with VC++.
I am surely
Hello Earnie,
On Mar 4, 2013, at 1:25 PM, Earnie Boyd wrote:
> On Mon, Mar 4, 2013 at 5:01 AM, Sebastian Wolff wrote:
>>
>> I modified the specs according to the Jon's summary of your recommendations,
>> i.e.:
>> - use -lmsvcr90 instead of -lmsvcrt
>> -
Hello Kai,
>>
>
> So there shouldn't be much trouble about that beside that newer
> runtime might uses additional exports not present by default in the
> default-version msvcrt.dll.
>
Thanks for giving me the assurance at this point. I want to add, however, that
the third-party lib may (and d
Hello Peter!
>>
>> I use Mingw-w64 distributed with OpenSuse Linux 12.2 64 Bit (based on Gcc
>> 4.7.2). I need to call a function from a (static!) third-party library which
>> was compiled using VC++ 9.0 (VS2008) targeting amd64, file name:
>> the_third_party_lib.lib. the_third_party_lib.l
Dear list!
first of all: Thanks for providing MingW-w64. Nevertheless, I fell into a
problem that I can not solve without help. Now I hope someone of you can give
me some advice to solve it.
I use Mingw-w64 distributed with OpenSuse Linux 12.2 64 Bit (based on Gcc
4.7.2). I need to call a func
13 matches
Mail list logo
