Matt England wrote:
At 4/18/2006 11:56 AM, Brad King wrote:
I think it's a Mandrake 10 box.
There is a bit of a trick needed for CMake due to support for loaded
commands. We link statically against everything but libc and libdl.
In order to work with the system libc on every other machine
Matt England wrote:
At 4/13/2006 10:42 AM, Matt England wrote:
I see that CMake does provide a single-binary set for all Linux
platforms:
http://www.cmake.org/files/v2.2/cmake-2.2.3-x86-linux.tar.gz
How is this done?
After a few days' posting and research, some references I found follow.
At 4/18/2006 09:43 AM, Brad King wrote:
We have a least-common-denominator Linux system. We build the needed
system libraries statically (such as curses). We build our own gcc using
the --disable-shared configure script option to avoid getting a shared C++
library. Look in the
Matt England wrote:
At 4/18/2006 09:43 AM, Brad King wrote:
We have a least-common-denominator Linux system. We build the needed
system libraries statically (such as curses). We build our own gcc
using the --disable-shared configure script option to avoid getting a
shared C++ library.
At 4/18/2006 11:56 AM, Brad King wrote:
I think it's a Mandrake 10 box.
There is a bit of a trick needed for CMake due to support for loaded
commands. We link statically against everything but libc and libdl. In
order to work with the system libc on every other machine you need to
build
At 4/13/2006 10:42 AM, Matt England wrote:
I see that CMake does provide a single-binary set for all Linux platforms:
http://www.cmake.org/files/v2.2/cmake-2.2.3-x86-linux.tar.gz
How is this done?
After a few days' posting and research, some references I found
follow. Alas, there seems to
