ary 20, 2018 at 3:50 PM
To: "Moreland, Kenneth" <kmo...@sandia.gov>
Cc: "cmake@cmake.org" <cmake@cmake.org>
Subject: [EXTERNAL] Re: [CMake] Latest versions of CMake/Qt Creator lock up
configuration on CMake error
Hi Ken,
On Tue, Feb 20, 2018 at 4:08 PM, Moreland,
This might be a question for the folks at Qt, but I thought I would float it
here first as other CMake users might have run into it.
This morning I updated to the most recent versions of CMake (3.10.2) and Qt
Creator (4.5.1). I then tried to use Qt Creator to configure a non-trivial
CMake
Does anyone know of a simple way to get CMake to time how long it takes to
compile each target? As it stands now, when compiling a CMake-managed project a
status is printed before each target is built. What I am looking for is a way
to get CMake to print a second status message after the target
The easiest solution is to simply copy UseLATEX.cmake to your project and
update it by hand when necessary, which is probably never. That's what I do.
-Ken
Sent from my iPad so blame autocorrect.
On Aug 1, 2013, at 10:45 AM, Zaak Beekman
zbeek...@gmail.commailto:zbeek...@gmail.com wrote:
Hi,
This sounds interesting. You might consider adding a page to the cmake wiki to
make it easier to find. You could make a link off this page listing
contributions from users.
http://www.cmake.org/Wiki/CMake_User_Contributed_Macros
-Ken
Sent from my iPad so blame autocorrect.
On Oct 27, 2012,
It looks like the CMake Wiki recently got spammed. I see several links were
recently added that do not belong (head lice treatment?). Even more annoying,
it looks like the spammer removed some links that do belong there.
-Ken
Kenneth Moreland
*** Sandia National
, Moreland, Kenneth kmo...@sandia.gov wrote:
Looking at the source code, I believe it is assumed that the paths you give
for images are relative to the directory ADD_LATEX_DOCUMENT is called. If
you make it an absolute path, UseLATEX.cmake will look in the wrong
directory for your images, find none
Looking at the source code, I believe it is assumed that the paths you give for
images are relative to the directory ADD_LATEX_DOCUMENT is called. If you make
it an absolute path, UseLATEX.cmake will look in the wrong directory for your
images, find none, and do no conversions. That would
UseLATEX.cmake has no facilites for docbook. It was designed strictly with the
latex and pdflatex programs in mind.
-Ken
On 11/18/10 2:59 PM, luxInteg lux-in...@btconnect.com wrote:
Greetings
I am learning cmake
I downloaded CMakeUseLatex from
http://www.cmake.org/Wiki/CMakeUserUseLATEX
, 2010, at 11:17 AM, Moreland, Kenneth wrote:
CMake comes with a FindLATEX.cmake module that will find the latex,
pdflatex, and related files. I have also posted a group of macros
that makes it quite easy to create CMake builds for LaTeX files.
The link is below.
http://www.cmake.org/Wiki
The reason the UseLATEX.cmake script copies files to the binary directory is
because the latex compiler has no equivalent to the -I flag. It always looks
for files with respect to the directory in which the command was run. Thus,
the easiest way to do an out-of-source build is to simply copy
requesting this ability...?
Thanks,
David
On Thu, Dec 17, 2009 at 8:37 AM, Moreland, Kenneth kmo...@sandia.gov wrote:
No. That does not help. I still get two entries on the dashboard. Is there
anything else I can do?
-Ken
On 12/16/09 2:38 PM, Alexander Neundorf a.neundorf-w...@gmx.net
For this particular use, doesn't the FindThreads package do this for you?
-Ken
On 12/17/09 7:43 AM, Nicola Brisotto nicolabriso...@gmail.com wrote:
Hello,
I've an autotools script to convert to cmake. It has a lot of long case
statement. Any tips to easily convert this statement?
Here an
I am setting up a ParaView dashboard for a cluster in which I have to compile
on one computer and then submit a job to run parallel tests on another
computer. This means I have to run one dashboard script to update and build the
code. At the end of this script I submit a parallel job to run
Consider using the UseLATEX.cmake collection of macros. It supports
out-of-source builds (in fact, sort of enforces them) and handles copying .sty
files as well as all sorts of other sticky little issues with building LaTeX
files. You can the macros and the documentation for them on this Wiki
wrote:
On Oct 26, 2009, at 8:13 AM, Moreland, Kenneth wrote:
Consider using the UseLATEX.cmake collection of macros. It supports
out-of-source builds (in fact, sort of enforces them) and handles copying .sty
files as well as all sorts of other sticky little issues with building LaTeX
files. You
I recently compiled Qt on my Mac with frameworks that contain both debug and
release versions of their libraries. I hoped (perhaps naively) that the debug
libraries would be used whenever I performed a debug compile of ParaView. No
such luck. The release libraries are always used. Does
Is there a way to add arguments to the invocation of make? In particular, I
want to add the -j flag to do parallel compiles. I tried setting the
CMAKE_MAKE_PROGRAM variable to /usr/bin/make -j8, but I get the following
error when I try to compile.
CMake Error: Generator: execution of make
PROTECTED] wrote:
On 18.08.08 14:02:29, Moreland, Kenneth wrote:
Is there a way to add arguments to the invocation of make? In particular, I
want to add the -j flag to do parallel compiles. I tried setting the
CMAKE_MAKE_PROGRAM variable to /usr/bin/make -j8, but I get the following
error
I assume that proposal.latex is either the man LaTeX document or one if the
INPUTS passed to ADD_LATEX_DOCUMENT. In this case, that file is copied over to
the build directory as part of the build process. CMake considers the file in
the binary directory a built file, and thus it is
I just posted a change to UseLATEX.cmake on the Wiki that removes the
un-feature of requiring all input files to be .tex files.
Thanks for the suggestion.
-Ken
-Original Message-
From: [EMAIL PROTECTED] [mailto:cmake-
[EMAIL PROTECTED] On Behalf Of Eric Noulard
Sent: Wednesday,
Are there any plans for a more cross-platform mechanism for building a
64bit build? Perhaps there could be an option for ADD_LIBRARY and
ADD_EXECUTABLE that told CMake whether to build for 32 bit or 64 bit.
I'm thinking of something equivalent to the STATIC/SHARED flags on
ADD_LIBRARY. I
I just upgraded to CMake 2.4.5 on my Mac and did a fresh build of
ParaView 3. The build failed with a link error concerning the python
libraries. I inspected the CMake variables and noted that
PYTHON_DEBUG_LIBRARY was set to -framework Python, but PYTHON_LIBRARY
was set to
Because of many changes in the Qt build processes, the CMake commands
for compiling against Qt4 have changed a bit from those for Qt3. For
example, commands like QT_WRAP_UI have new QT4_WRAP_UI macros to handle
the new Qt4 commands.
I suggest taking a look at FindQt4.cmake to see more details on
Title: RE: [CMake] How to contribute FindXXX cmake module?
I also recommend posting your FindXXX files to the CMake Wiki:
http://www.cmake.org/Wiki/CMake_User_Contributed_Macros
In the best case scenerio, it will take several months for a CMake contribution to be available in a general
The QT_QTMAIN_LIBRARY and QT_USE_QTMAIN variables are broken as of CMake
2.4.1. They should be fixed on the trunk and when CMake 2.4.2 is
released.
-Ken
-Original Message-
From: [EMAIL PROTECTED] [mailto:cmake-
[EMAIL PROTECTED] On Behalf Of Cristian Adam
Sent: Wednesday, May 17,
I just ran into the same and John Biddiscombe where vtkConfigQt.cmake
has backslashes in some strings. After investigation, I learned that
the problem is that FindQt4.cmake makes two versions of the
QT_MOC_EXECUTABLE and QT_UIC_EXECUTABLE variables: a cached version and
a non-cashed version. The
How could I tell cmake to default build pdf instead of dvi ?
Add DEFAULT_PDF to the ADD_LATEX_DOCUMENT arguments.
-Ken
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Sigh. I still don't see what can be wrong. Can you send me a tarball
of everything? Maybe something gets lost when I try to duplicate your
build.
-Ken
-Original Message-
From: Bertrand Jacquin [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 25, 2006 4:03 PM
To: Moreland, Kenneth
Maybe could you it to me. Maybe a wiki malformation ?
I've attached the file.
Did you go there :
http://guybrush.ath.cx/gitweb/?p=school/PFE.git;a=tree;h=bj/cm
ake;hb=bj/cmake
That's a slightly different link than you sent before. I got the
CMakeLists.txt in question and tried it out.
I got the
CMakeLists.txt in question and tried it out. Apart from
adding the
.cmake extension to the file in the INCLUDE command,
everything worked
fine.
If a add .cmake to extension, cmake try to find a file called
UseLATEX.cmake.cmake. So, I trashed it.
I see. You put
version of CMake are you using?
-Ken
-Original Message-
From: Bertrand Jacquin [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 20, 2006 9:36 AM
To: Moreland, Kenneth
Cc: Bertrand Jacquin; cmake@cmake.org; else-devel@gna.org
Subject: Re: [CMake] RE: UseLATEX.cmake macros
On 4/19
And UseLATEX.cmake build dvi. I don't know how to tell him to
don't build dvi files.
Build the pdf target (make pdf). That will use pdflatex.
Also, why is it neccessary to build in another directory than
source directory ?
Because UseLATEX.cmake will run configure on your .tex files.
And UseLATEX.cmake build dvi. I don't know how to tell
him to don't
build dvi files.
Build the pdf target (make pdf). That will use pdflatex.
It doesn't work here.
~/tmp/PFE % make pdf
Building image files for ps documents.
-- Check for working C compiler: gcc
-- Check for
With the ADD_EXECUTABLE command, you can specify several MACOSX_BUNDLE_*
options for the resulting bundle, but I cannot find any documentation on
what each one means. Is there any?
-Ken
Kenneth Moreland
*** Sandia National Laboratories
***
*** *** *** email:
The function you are looking for is called QT4_WRAP_UI (not
WARP).
You will also need to add an INCLUDE(${QT_USE_FILE}) after
finding Qt 4.
-Ken
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of xavier
delannoySent: Tuesday, January 17, 2006 8:40 AMTo:
36 matches
Mail list logo
