Do you know if they work on Borland, MinGW, and cygwin as well as VS?
I don't see why not. A .lib file isn't very sophisticated, why
wouldn't they? I can't test any of those at the moment because the
Mingw I have is the modified one from U++ that doesn't work with
CMake, unfortunately.
Warren Turkal wrote:
On Monday 02 October 2006 08:38, Brad King wrote:
http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_li
There are some references to 2.2 being the current release and having to use
the current development for some features. Presumably, this info
James Mansion wrote:
Are you trying to link object files compiled without -fPIC into a shared
library? That would never work; -fPIC is required for all objects in shared
libraries.
I'm guessing so - I want to do it too! Or rather, be able
to make a static library containing objects that
On Monday 02 October 2006 08:38, Brad King wrote:
http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_li
There are some references to 2.2 being the current release and having to use
the current development for some features. Presumably, this info should be
updated with
http://www.cmake.org/Wiki/CMake_FAQ#Does_CMake_support_.22convenience.22_lib
raries.3F
The FAQ is misleading - they DO make sense for (all) non-UNIX linkers. What
non-UNIX linkers do not have an equivalence to an archive?
There is no reason why I cannot compile a load of objects with DLL
On 2006-09-26 17:06-0600 Abe Stephens wrote:
When I build object files for shared library targets cmake includes the
position independent code flag (-fPIC). However when I build objects for
static library targets the flag is omitted. I try to link the static lib to
other objects in a shared
