Bill Hoffman wrote:
> [...]
> I think you are going to have to use regular expressions.
> [...]
Hello,
if you want some code that can correctly identify matching quotation
marks, regular expressions don't have enough expressive power to
describe that behaviour (you would need something like PEGs
Matthew Woehlke wrote:
> [...] So I think I still have the same problem, how to take a string
> that might look like '-lfoo -lbar -L"foo bar/thelib"' and split it
> into '-lfoo', '-lbar' and '-L"foo bar/thelib". From there I can use
> STRING to strip the flag and SET/LIST to build the needed varia
Hendrik Sattler wrote:
> [...]
> Windows needs the indirect dependencies, same as MacOS X, AFAIK.
> [...]
Hello,
I'm not so sure about the precise architecture on Windows and Linux, but
the MacOS X linker *does not* require indirect dependencies to be
mentioned explicitly when creating an execut
Teodor Calin Hanchevici wrote:
> Alan, this does not work either,
> LINK_FLAGS "/nodefaultlib:LIBCMT.lib;/nodefaultlib:MSVCRT.lib"
> it always picks the first one
> [...]
Hello,
the LINK_FLAGS property has to be set to a simple space separated string
just like it is supposed to appear on the li
Bill Hoffman wrote:
> [...]
> -search_paths_first
> [...]
> If you add that to LDFLAGS before you run cmake it should fix the
> problem. At one point,
> I thought we made this a default flag in CMake. I guess it never got
> commited, what
> do you mac folks think, should this be a default fla
[EMAIL PROTECTED] wrote:
> [EMAIL PROTECTED] wrote:
>
>> [...]
>> When I TARGET_LINK_LIBRARIES( test /path/to/libA.lib) I get the equivalent
>> of -L /path/to -l libA.lib. I'd like to get -l /path/to/libA.lib. Is
>> that possible?
>
> Currently this is not possible. You also shouldn't need it.
Manfred Rebentisch wrote:
> [...]
> on my Debian-Backup-Server I dont need g++ but only gcc. How can I avoid the
> following error:
>
> -- Check for working CXX compiler: CMAKE_CXX_COMPILER-NOTFOUND
> CMake Error: your CXX compiler: "CMAKE_CXX_COMPILER-NOTFOUND" was not found.
>
> Please set
Hello,
part of the issues I had with creating and linking to libraries on MacOS
X have been resolved with help from this list. But the most important
problem remains.
I'm using CMake 2.4.6 on a PowerPC iBook running MacOS X 10.4.8 and I
can't get CMake to link against a static library if a dynami
Brandon J. Van Every wrote:
> [...]
> I just checked the file doc/cmake-2.4/cmake.html in
> http://www.cmake.org/files/v2.4/cmake-2.4.6-Darwin-universal.tar.gz
> and it correctly documents CLEAN_DIRECT_OUTPUT.
> [...]
I used the .dmg based installer instead of the tarball you examined.
Although I
Brandon J. Van Every wrote:
> [...]
> This capability was added relatively recently, maybe in CMake 2.4.5.
> What version of CMake are you using?
> [...]
Hello,
as I said in my original mail, I'm running the most recent release
available for download, which is CMake 2.4.6 at the moment. I trie
Brandon J. Van Every wrote:
> Thomas Christian Chust wrote:
>
>> I consider this seriously buggy behaviour. First of all I don't like it
>> that the build system magically wipes out one of the library targets I
>> ordered it to create.
>
> [...] T
Hello,
I'm using CMake 2.4.6 on a PowerPC iBook running MacOS X 10.4.8 and I
found some issues with building both shared and static libraries and
with linking to static libraries using CMake.
I have attached a very simple example project to this e-mail that can be
used to demonstrate the problems
12 matches
Mail list logo
