Quiet roof goes leisurely: how to make static library compiled in GCC and MSVC?

0 like 0 dislike
7 views
So, we have a static library, a collection of 4 options (for each of the compilers in debug and release):

— i686-pc-cygwin-gcc (-mno-cygwin)

— gcc from the MinGW package


debug@i686-pc-cygwin-gcc to link with the host project in the Studio to cheer, even works :)

release@i686-pc-cygwin-gcc does not link with the host project in the Studio, swears by __alloca (MS-libraries there is, but it's called _alloca).

debug@mingw-gcc does not link with the host project in the Studio swears on __chkstk

release@mingw-gcc link with the host project in the Studio, but not working (cresida).


Who deal with it, how to collect? Judging by the results, can be collected, the truth is somewhere near.
by | 7 views

3 Answers

0 like 0 dislike
Can't tell about Cygwin, but with MinGW it is necessary to take not less GCC 4.5.1. It was there in the project mingw-w64 have done extensive work on compatibility with MSVC. More details or need to smoke their wiki, or to kick the developers in the IRC channel of the project (the second is usually more effective).
by
0 like 0 dislike
What is different from _alloca _alloca?
by
0 like 0 dislike
Not that much help, i686-w64-mingw32-gcc (4.5.1) C-O0 -g has collected a library which references
___chkstk (3 "_") and __stricmp (2 "_"). Sit scratching head on
by

Related questions

0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
1 answer
0 like 0 dislike
3 answers
0 like 0 dislike
1 answer
110,608 questions
257,186 answers
0 comments
28,758 users