Hi all,
We have reported an issue. It is regarding conversion of existing Visual Studio
.targets files to cmake.
The link for the reported issues is as follows.
http://www.cmake.org/Bug/view.php?id=15044
Kindly let us know if this can be done in cmake.
Thanks & Regards
Ravi Raman
Xoriant Solut
Please ignore the post. I found out what's wrong - human error :( I forgot to
copy the modified CPackRPM.cmake to cmake's system Modules subdirectory.
Problem solved.--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
K
Thanks Norman,
Spot on – definitely feeling like we’re running against the grain here. Will
check out the Cmake package as that sounds like a good example.
Cheers,
Lachlan Hetherton
Software Engineer (Visualisation)
☎ +613-9545-8041
From: "Williams, Norman K"
mailto:norman-k-willi...@uiowa.ed
Hi Sean,
The confusion I am having about deploying in a .app is:
1. We currently ship with >1 executable. .app bundles are only supposed to
have 1 executable (I think)
2. Our application is designed to allow others to build plug-ins for it.
Not sure how this works if we deploy as a .app. Maybe we
On 29.07.2014 23:42, Eric Clark wrote:
Hello All,
I have had this problem with CMake for quite some time now. I have
posted the question to this message board once before, but did not
figure out a solution. Whenever I try to run cmake on a
cmake_install.cmake file with all of the appropriate
Hello All,
I have had this problem with CMake for quite some time now. I have posted the
question to this message board once before, but did not figure out a solution.
Whenever I try to run cmake on a cmake_install.cmake file with all of the
appropriate defines set, I always get at least one er
On linux, at least, this results in there being double quotes around the
||, which causes it to not be interpreted by the shell.
B.
On 07/29/2014 12:25 PM, Glenn Coombs wrote:
I think this works like you want:
cmake_minimum_required(VERSION 2.6)
set(DO_RELAX 1)
if(DO_RELAX)
set(OR_RELAX
I think this works like you want:
cmake_minimum_required(VERSION 2.6)
set(DO_RELAX 1)
if(DO_RELAX)
set(OR_RELAX || echo \"no big deal\")
else()
set(OR_RELAX)
endif()
add_custom_command(OUTPUT foo COMMAND generate-foo ${OR_RELAX} VERBATIM)
add_custom_target(do-foo ALL DEPENDS foo)
--
Gl
can try removing the quotes and subst space for semicolon?
On Tue, Jul 29, 2014 at 11:13 AM, Bill Newcomb wrote:
> That doesn't work either:
>
> foo:
> $(CMAKE_COMMAND) -E cmake_progress_report
> /home/bnewcomb/tmp/cmake-tests/custom-or/CMakeFiles $(CMAKE_PROGRESS_1)
> @$(CMAKE_
That doesn't work either:
foo:
$(CMAKE_COMMAND) -E cmake_progress_report
/home/bnewcomb/tmp/cmake-tests/custom-or/CMakeFiles $(CMAKE_PROGRESS_1)
@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold
"Generating foo"
generate-foo "|| echo \"no big deal\""
I would look at how CMake itself is packaged for release.
The ‘one executable per App bundle’ is Apple-centric thinking that luckily is
not enforced. That isn’t how CMakes (or the OS X Emacs, e.g.) works. You can
have whatever you want in an app bundle.
It does means that after install, users
RHEL 7.0 (and its free rebuilds, e.g. CentOS 7.0) is bundled with newer rpm
which rigorously checks whether a package declare system directories or not. If
a package does, then it would issue an error like what's shown below:
Transaction check error: file /usr from install of cmake-3.0.0-1.x86_6
On Tue, 29 Jul 2014 01:06:26 +, lachlan.hether...@csiro.au said:
>I’m currently looking into the OSX Bundle generator, however, our
>application ships with multiple executables and a number of dependent
>libraries and frameworks, so I’m not quite sure whether this is the
>right way to go. From
Hello,
I've got an executable built using cmake.
I use ctest to test my executable. Each time the executable is executed, a log
file on std::cout is produced.
I the log file, I added the following XML tags:
0.33
I don't see these named measurements in the xml file produced by ctest -D
NighlyS
We use a "Configured" bash shell script for our OS X deployment which consists
of a Top level directory with the .app bundles and a "tools" folder. The shell
script ensures all the libraries have all the proper install_paths encoded,
thin all the binaries to a single 64 bit arch and some other c
15 matches
Mail list logo
