On Saturday 17 January 2009 01:40:27 Timothy M. Shead wrote:
Agreed - as I mentioned before, I understand that if you don't have a
bundle, running a GUI application out of the build directory is
problematic (for those unfamiliar: your program runs, but the window
manager doesn't provide any
hi list,
I'm having a little problem involving c++ static initializations using
static libraries libraries. The problem is that if I link this code to the
executable as a static library the code is never run, but if it is a SHARED
library it is, but I need it to be static (if possible).
The code
This problem may occur with gcc because of static library linking policy. If
you have a symbol in static library which is not referenced from main
executable it will not be linked in. (For example, if you use static classes
to register something to factories). To solve this issue, you should
Alternatively, you could explicitly reference all the symbols of interest
from the main executable. That gives you just what you need, still allowing
the linker to strip out the unreferenced things you don't need.
Another benefit of this approach is that you'll end up with some code that
shows
Robert Dailey schrieb:
I've specified a very complex CMake script that generates an
executable project. When I use this CMake script to generate a Visual
Studio 2008 project, the Import Library property located in Project
Settings Linker Advanced property page in Visual Studio 2008 has
a
On Sat, Jan 24, 2009 at 11:16 AM, Stefan Buschmann s_buschm...@gmx.dewrote:
Robert Dailey schrieb:
I've specified a very complex CMake script that generates an executable
project. When I use this CMake script to generate a Visual Studio 2008
project, the Import Library property located in
