Hi,
Henning Nielsen Lund wrote:
Just a litle important question... are we going to use clib2 or newlib?
It depends. Clib2 has more functionality, newlib is shared, which is a big advantage (considering the amount of stuff binaries).
The best idea is to make it "selectable" in all the makefile we create ourselves (with configure, it's done at configure time, anyway). Take a look at how I solved that in the polygon clipper makefile. The "-mcrt=lib" option makes this rather simple.
Of course, only the new, unreleased compiler has this stuff, but we're going to release a new SDK soon, plus, we're moving the compiler and tools from our internal CVS over to sourceforge.
Regards,
Hello Thomas,
On 2005/0622, you wrote:
Hi,
Henning Nielsen Lund wrote:
Just a litle important question... are we going to use clib2 or newlib?
It depends. Clib2 has more functionality, newlib is shared, which is a big advantage (considering the amount of stuff binaries).
Couldn't you convince Olaf to make Clib2 to a shared library ;-)
The best idea is to make it "selectable" in all the makefile we create ourselves (with configure, it's done at configure time, anyway). Take a look at how I solved that in the polygon clipper makefile. The "-mcrt=lib" option makes this rather simple.
Good idea :-)
Of course, only the new, unreleased compiler has this stuff, but we're going to release a new SDK soon, plus, we're moving the compiler and tools from our internal CVS over to sourceforge.
Nice, I am sure that this is going to be very welcome around the world :-)
Regards,
Best regards Henning
-
Henning Nielsen Lund -
Thomas Frieden