Hi J Decker,
sorry I've missed your answer, while I wrote mine.
Now I used install( PROGRAMS ...instead of FILES
but I can't see any difference in the output. The error message is exactly
the same as in my last reply.
To be sure that it is not a cache problem, I deleted the 'build' dir
To Eric's point: your destination for these files should probably be "bin"
and not "/usr/bin". That way from CPack you can set the "
CPACK_INSTALL_PREFIX" to point to the actual place you want to install your
project.
But everything still comes down to this: if your above prefix is "/usr"
then
Oops, sorry, confused with different variants.
I've tried
$SET CC=D:\LLVM-3.7.1\bin\clang-cl.exe
$SET CXX=D:\LLVM-3.7.1\bin\clang-cl.exe
$cmake -G "Ninja" ..
Compilation succeeded, linkage has ended up with "clang-cl.exe: error:
unable to execute command: program not executable".
The same
Yes, when using 'bin' instead of '/usr/bin' ( with PROGRAMS and without
RUNTIME) it works.
But nevertheless it's a bit sad because I used the absolute paths with
consideration for two reasons:
1. As I mentioned it's a Qt/KDE program (still version 3 at the moment).
Depending on the target distro
2016-03-09 19:50 GMT+01:00 Winfried :
> Yes, when using 'bin' instead of '/usr/bin' ( with PROGRAMS and without
> RUNTIME) it works.
>
> But nevertheless it's a bit sad because I used the absolute paths with
> consideration for two reasons:
>
> 1. As I mentioned it's a Qt/KDE
Hi,
I'd like to experiment writing a Preference Pane for Qt-based apps. I'd prefer
to use CMake instead of Xcode and wonder if someone can point me to an example
CMake file that generates a proper .prefPane bundle? I'm not having much luck
googling for one for now.
Thanks,
René
--
Powered
Eric Noulard wrote
> 2016-03-09 19:50 GMT+01:00 Winfried
> winkus4u@
> :
>
>> Yes, when using 'bin' instead of '/usr/bin' ( with PROGRAMS and without
>> RUNTIME) it works.
>>
>> But nevertheless it's a bit sad because I used the absolute paths with
>> consideration for two reasons:
>>
>> 1. As
2016-03-09 20:27 GMT+01:00 Eric Noulard :
>
>
> 2016-03-09 19:50 GMT+01:00 Winfried :
>
>> Yes, when using 'bin' instead of '/usr/bin' ( with PROGRAMS and without
>> RUNTIME) it works.
>>
>> But nevertheless it's a bit sad because I used the absolute
Hi Cristian,
That's what I did:
1) Created empty directory "D:\CL", moved clang-cl.exe there and renamed
it to cl.exe.
2) Put the paths to cl.exe and Clang first in the global PATH
environment variable. Set path to Clang Includes first in INCLUDE
3) Launched Cmake from an empty project dir.
Hi Benjamin,
thanks for the idea, tried to use simple paths, unfortunately it doesn't
solved the problem.
the path to your compiler seems to have spaces in it. I had problems
on Windows with spaces or other special characters in the compiler
path, too. Please try to locate the compiler in
On Wed, Mar 9, 2016 at 9:27 PM, Nicholas Braden
wrote:
> I'm not sure which discussion you're referring to, so forgive me if
> this was already mentioned - but are you using a superproject to
> ensure that dependencies are built and installed before your own
> project?
2016-03-09 22:12 GMT+01:00 Winfried :
> Eric Noulard wrote
> > 2016-03-09 19:50 GMT+01:00 Winfried
>
> > winkus4u@
>
> > :
> >
> >> Yes, when using 'bin' instead of '/usr/bin' ( with PROGRAMS and without
> >> RUNTIME) it works.
> >>
> >> But nevertheless it's a bit sad because
(This is really a continuation of a discussion from 25/26 January.)
I'm still confused about ExternalProject_Add and libraries.
I'd like to get to the point where I (or more likely a process
somewhere) can check out a project, then run cmake and ninja (or make
or whatever) and have that build
I'm not sure which discussion you're referring to, so forgive me if
this was already mentioned - but are you using a superproject to
ensure that dependencies are built and installed before your own
project? That is, all dependencies as well as your own project are
built via ExternalProject_Add and
> -- check which cl.exe is used:
> $which cl
> D:\CL\cl.EXE
>
> -- trying to build:
> $cmake -G "Ninja" -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang ..
If your goal is use your renamed clang-cl (cl.exe) then why are you
telling CMake to use to use clang.exe ?
You can clearly see
"install(FILES..." should work, that is how you install non-target files.
Are you sure it isn't a permission issue? Do other install commands work
that copy to /usr/bin?
We'll need a little more information to diagnose the issue, an simple CMake
example would be nice.
Caleb
On Wednesday, March
Here we migrated a huge Visual Studio solution (130 targets) to CMake.
* The switch between Debug and Release always took a few seconds, during
with Visual seems freezed.
* We have the same problem : I think the cmake generator has to modify
vcxproj files and when a file like this, Visual studio
Hi,
the build system of a qt-based visual robot programming teaching platform
shall be ported from autotools to cmake.
For the build process of the platform the underlying compilers and some
shell scripts aiming diffenent robot targets are not built but just have to
be installed (copied) to
use INSTALL( PROGRAMS ) ... FILES drops executable bit on linux
On Wed, Mar 9, 2016 at 5:38 AM, J. Caleb Wherry wrote:
> "install(FILES..." should work, that is how you install non-target files.
> Are you sure it isn't a permission issue? Do other install commands work
>
Hi Caleb,
yes, I also suppose that it's some kind of permission issue, but I don't
know how to handle it:
All other install commands work exept those that should also copy to
/usr/bin.
I also tried to install those with another order, here is that code form
subdirectory 'tools':
install( FILES
Hi folks,
Trying to cross-compile, passing the toolchain as usual:
cmake -DCMAKE_TOOLCHAIN_FILE=/path/to/Toolchain.cmake <...>
And forwarding CMAKE_TOOLCHAIN_FILE variable down to my external projects, like
so:
ExternalProject_Add(${app}
# ...
CMAKE_CACHE_ARGS
2016-03-09 16:58 GMT+01:00 Winfried :
> Hi Caleb,
>
> yes, I also suppose that it's some kind of permission issue, but I don't
> know how to handle it:
>
> All other install commands work exept those that should also copy to
> /usr/bin.
> I also tried to install those with
_VERSION_MINOR 5)
-set(CMake_VERSION_PATCH 20160309)
+set(CMake_VERSION_PATCH 20160310)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 96f661517d1e98a7a940f16781e6713745074e2a (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 49cff25ca3e667d6d5a20a6b64ed55ef875890c1 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 730be0e891795f3cbbc6e506a52b7bb612eb1fbb (commit)
via
On Tue, Mar 08, 2016 at 12:36:31 +0100, Nicolas Desprès wrote:
> Did you have a chance to review my patches?
So I looked at it today, and it looks good overall. A few niggles:
+inline bool cmEndsWith(const std::string& str, const std::string& what)
+{
+ assert(str.size() >= what.size());
On 03/09/2016 04:13 AM, Charles Huet wrote:
> We used to use this, by creating a composite image containing the reference,
> generated and diff, but in some cases comparing accurately was tedious.
> Having the 3 images separately allows us to open each in a tab and quickly
> switch from one to the
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 9e21a254790a6998010de0ac969a16d863a09182 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via ca274d39b7172c603b2c8e66175aa2838627b70d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via d1856e2e333001d0f106a3af86dfe000fd61b2b2 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via 345d5926ee01d716f11c9bf8380fec180088d5a3 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, master has been updated
via b19bc31277bb2e3dd75e78f64924be3955ea8c6d (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 6f92f9c5ead82168eba18ada867b25ce69c37fd3 (commit)
via
Hi,
Is there someone able to help me regarding ctest usage with labels?
Here is the problem: I have various tests which have labels attached to them:
set_property (TEST test1 PROPERTY LABELS LABEL1)
set_property (TEST test2 PROPERTY LABELS LABEL1 LABEL2)
set_property (TEST test3 PROPERTY LABELS
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via ed3c228dc0ae7145a581c16278ffb2a534299403 (commit)
via
On 02/27/2016 09:38 AM, Mariusz Pluciński wrote:
> Following is the list of patches with descriptions:
Thanks!
> 1. kwsys: fix build on VS Clang/C2 toolset
> Makes it possible to build CMake itself with Clang/C2.
Applied to KWSys [upstream] (http://review.source.kitware.com/#/c/20856/)
and
On Tue, Mar 08, 2016 at 12:36:31 +0100, Nicolas Desprès wrote:
> Did you have a chance to review my patches?
Sorry, not yet. I hope to have a peek at it today or tomorrow.
--Ben
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 6ff0e39f41989d845d9a76511181791966eab28c (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via aabb3f247d1846ae8c65b80477119fd90c24dfc5 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "CMake".
The branch, next has been updated
via 8eb1b66b1259d4940c66ab3665f1e64c75cb0271 (commit)
via
Thank you!
Experimental installer (based on IFW generator):
Windows offline 32-bit (MSVC2013):
http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-win32-x86.exe
Windows offline 64-bit (MSVC2013):
http://ifw.podsvirov.pro/cmake/files/v3.5/cmake-3.5.0-win64-x64.exe
Today online master:
Sadly this is quite not good enough.
We used to use this, by creating a composite image containing the
reference, generated and diff, but in some cases comparing accurately was
tedious.
Having the 3 images separately allows us to open each in a tab and quickly
switch from one to the other, making
Hello.
I checked the generation performance for our huge project for Linux and
Windows, and there is big improvement for 64bit over 32 bit for Linux.
For Windows there is no such big difference between 32bit and 64bit in
generation time:
CMake 3.5.0 Windows 64 bits:
End time: 9.41:45
44 matches
Mail list logo