Have you tried building your project using a different generator to check if
it's a VS-specific problem?. I've set compile flags on a per-source basis
using various generators under Linux and had no problem. Do you have access
to a Linux box, or is your project Windows-specific?
Cheers,
Adolfo
Right now I don't have access to a linux system so I can't check. But my
very reason to use cmake
is to have a bulid system which works on windows in addition to unix (on
which I have autotools),
so it's kind of unimportant whether it works on linux or not :)
Best regards,
Yevgen
Adolfo
On 12.04.09 15:54:43, Yevgen Muntyan wrote:
Andreas Pakulat wrote:
On 07.04.09 20:29:49, Yevgen Muntyan wrote:
I want to convert an autotools project to cmake. But, I don't know
how to solve the problem of the
convenience libraries. The issue is: the project builds a shared
library of
Hi!
I have managed to solve my problems just the way Robert proposed. I changed
the cMakeOptions.cmake file fixing the lines:
find_package(VTK REQUIRED)
include(${VTK_USE_FILE})
and using the VTK_WRAP_TCL3 with the required parameters.
Thank you very much for the useful info.
Jorge,
2009/4/6
Piotr Dobrogost wrote:
Bill Hoffman wrote:
It was a mistake
to have CMAKE_CXX_FLAGS and CMAKE_C_STANDARD_LIBRARIES be strings they
should have been lists.
I'm glad you said this. It's something I've been trying to show in my posts.
Certainly CMAKE_C_STANDARD_LIBRARIES should have been a
Hello,
I thought someone here might be interested in this discussion in the
Blender developer mailing list:
http://lists.blender.org/pipermail/bf-committers/2009-April/023084.html
It's titled Removing Build Systems and they are discussing whether
it would be appropriate to drop a couple of
Brad King wrote:
Last year I started working on new features to allow projects to specify
flags with modern semicolon-separated lists. See my comment from
2008-10-09 here:
http://www.cmake.org/Bug/view.php?id=6493
It looks like that is the 3rd solution I suggested previously;
Another
Bill Spotz wrote:
So I was able to solve my problem of duplicate python target names
generated from SWIG interface files:
PyTrilinos/NOX/___init__.so
PyTrilinos/NOX/Epetra/___init__.so
by overhauling UseSWIG.cmake to take advantage of the OUTPUT_NAME
property of the