Hello List,
i m just trying cmake to build a small project. I m using Xml Stuff in it, so
my *.pro file had something like 'QT += xml'.
So far i think my CMakeLists.txt is right but the Xml lib is missing. CMake
succeeds but make fails claiming that QDomDocument is not declared.
My CMakeLists.
On 2007-05-05 09:41-0300 BrĂ¡ulio Oliveira wrote:
Hello all,
I'm having some problems on write code to handle .ts due to file
dependencies. So, I've made a small example of what I need to work. Here It
comes:
The three text files: a, b and c, all int the source directory. I write the
following
Matthew Woehlke wrote:
Trevor Kellaway wrote:
Hi,
The following snippet will send the strings "1", "2" and "3" to the
messages console, each of them on its own line:
SET(FOO "1 2 3")
STRING(REPLACE " " ";" FOO_LIST "${FOO}")
FOREACH(item ${FOO_LIST})
MESSAGE(${item})
ENDFOREACH(it
Hello all,
I'm having some problems on write code to handle .ts due to file
dependencies. So, I've made a small example of what I need to work. Here It
comes:
The three text files: a, b and c, all int the source directory. I write the
following code:
ADD_CUSTOM_COMMAND(OUTPUT a
Christoph John wrote:
Hello Bill,
Using Target_Link libaries even does not work for me. I used the following
construct:
SET( VXL_DEBUG_LIBS "D:/vxl-1.8.0/lib/debug/vcl")
SET( VXL_RELEASE_LIBS "D:/vxl-1.8.0/lib/release/vcl")
TARGET_LINK_LIBRARIES(TheApp optimized ${VXL_RELEASE_LIBS} debug
${VX
Kitware is seeking to fill positions immediately. We are looking for talented
individuals who will relocate to the Albany, NY USA area, are willing to work in
a small company, and show flexibility in work assignments. Valued skills
include C++, VTK, ITK, CMake, web development, large data visual
Kishore,
> OK. Personally, I use KDevelop and do not have first hand
> experience with this kind of use. In past discussions, I
> learnt that it is possible to use the GCC compiler when
> building from VS. The downside being that error parsing won't
> work. So no click-on-error-message to show
Hi,
> # You can ignore the
> GenericBuildPrologue.cmake/GenericBuildEpilogue.cmake
> # related stuff, as this is my ported existing build world
> support, and is # a bit too specialized, although it may have
> the odd useful CMake trick # in it, I don't claim to be an
> expert, far from it, I'