Mike Melanson wrote:
> Brad King wrote:
>> You can link the entire program statically if you don't have any of your
>> own shared libraries. Then running "ldd myexe" will produce a message
>> that the executable is not dynamically linked. This requires just
>> adding "-static" to CMAKE_EXE_LINKER
Brad King wrote:
You can link the entire program statically if you don't have any of your
own shared libraries. Then running "ldd myexe" will produce a message
that the executable is not dynamically linked. This requires just
adding "-static" to CMAKE_EXE_LINKER_FLAGS (or the appropriate option
Mike Melanson wrote:
> Brad King wrote:
>> This is not really a problem that a build system can solve directly.
>> The native build tools need to be configured to support it. In order to
>> link statically to the C++ runtime but dynamically to the C runtime and
>> other libraries you need to confi
Brad King wrote:
This is not really a problem that a build system can solve directly.
The native build tools need to be configured to support it. In order to
link statically to the C++ runtime but dynamically to the C runtime and
other libraries you need to configure the host system properly.
Mike Melanson wrote:
> I am working on a fairly large software project that I autotool'd some
> time ago. The build system has been working reasonably well. However, I
> have hit a possible limitation that I don't know how to solve with
> autotools. So I wanted to know if CMake can solve this probl
Hi,
I am working on a fairly large software project that I autotool'd some
time ago. The build system has been working reasonably well. However, I
have hit a possible limitation that I don't know how to solve with
autotools. So I wanted to know if CMake can solve this problem:
I need to stat