Dear list,
for the archive I want to note some more important details when linking
mingw-w64 against msvcr90.
Reminder: I patched the MinGW-w64 installation of openSuse (GCC 4.7.2) to
generate a libmoldname90.a and then set new GCC specs that link against
moldname90 and msvcr90 instead of mol
On Mon, Mar 4, 2013 at 10:42 AM, Sebastian Wolff wrote:
> Although little off-topic, one questions remains to me: Is it allowed to
> distribute proprietary software which links against libgcc statically?
http://www.gnu.org/licenses/gcc-exception-faq.html
--
Earnie
-- https://sites.google.com/sit
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
Hi Sebastian,
2013/3/4 Sebastian Wolff :
> 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
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
On Mon, Mar 4, 2013 at 7:50 AM, Sebastian Wolff wrote:
> I also checked all DLLs in Dependency Walker. The following DLLs reference
> msvcrt.dll: advapi32.dll, comdlg32.dll, netapi32.dll, ole32.dll,
> oleaut32.dll, ws2_32.dll
> Comparing this with the VC++-built executable gives similar implicit
>
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
>> - use -static
>> - avoid linking against -lm
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
> - use -static
> - avoid linking against -lmoldname
> - use the define -D__MSVCRT_VERSION__=0x0900 when compiling *.
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
> 2013/3/2 Jon :
> >> > There is one problem: There is no liboldname90 in Mingw-w64, hence I kept
> >> > liboldname.
> >> Yes, for what purpose you need it?
> >
> > I'm updating my 32/64bit build systems to better automate how I use
> > mingw/mingw-w64, and have three followup questions:
> >
> > 1
Hi Jon,
2013/3/2 Jon :
>> > There is one problem: There is no liboldname90 in Mingw-w64, hence I kept
>> > liboldname.
>> Yes, for what purpose you need it?
>
> I'm updating my 32/64bit build systems to better automate how I use
> mingw/mingw-w64, and have three followup questions:
>
> 1) Why do
On Sat, Mar 2, 2013 at 1:15 PM, Jon wrote:
>> > There is one problem: There is no liboldname90 in Mingw-w64, hence I kept
>> > liboldname.
>> Yes, for what purpose you need it?
>
> I'm updating my 32/64bit build systems to better automate how I use
> mingw/mingw-w64, and have three followup questi
> > There is one problem: There is no liboldname90 in Mingw-w64, hence I kept
> > liboldname.
> Yes, for what purpose you need it?
I'm updating my 32/64bit build systems to better automate how I use
mingw/mingw-w64, and have three followup questions:
1) Why do mingw-w64 based toolchains (rubenvb
Hello Sebastian,
2013/3/1 Sebastian Wolff :
> 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 1
On 01.03.2013 17:27, Sebastian Wolff wrote:
> 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
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
17 matches
Mail list logo
