30 Jun
2008
30 Jun
'08
9:54 p.m.
On Mon, 30 Jun 2008 11:12:46 +0200
"KJK::Hyperion" <hackbunny(a)reactos.com> wrote:
Colin Finck ha scritto:
I'd support that. I think my position on importing dependencies has reversed
over the years, and I now favor including them. Also, libgcc is small.
--
"Ask Bill why the string in function 9 is terminated by a dollar sign. Ask him,
because he can't answer. Only I know that".
- Gary Kildall
Unfortunately, it looks like it's unfixable
if we keep on directly using ld
for linking (as introduced in these revisions) instead of calling the gcc
frontend.
ld supports response files, like Microsoft tools:
@FILE Read options from FILE
(from ld --help)
Passing "-lgcc" also doesn't work,
because mingw32-ld only seems to search
for libraries in "mingw32/lib", not "lib/gcc/mingw32/4.1.3" as gcc
does.
let's import libgcc then. It makes sense to me for our build environment
to be completely self-contained