back in January and I was forced to reinstall everything on the machine
without encountering any problems like this. Any suggestions?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to su
ore recent version, and its
release notes don't say anything about this.
CMake Error at cmake/AddCeresCXX11RequirementsToTarget.cmake:70
(target_compile_features):
target_compile_features no known features for CXX compiler
"Clang"
version 9.0.0.939.
Any suggestions
ly in the hope that cmake would figure out that these files
were a Windows-only thing and ignore them, but that didn't really work. Is
there some easier way to do this? What we have is working well, but I'm
always looking for ways to reduce the number of conditional tests we
require in t
is driving us nuts, since we don't understand why the
check_c_source_compiler check is not working. Is there some way we
can get debug information about why the compile fails? That might
give us some clues.
Rick
On Mon, Sep 22, 2014 at 12:06 PM, Rick McGuire
wrote:
> We have some se
What are we missing here? Is
there some technique we should be using that will work across the
various platforms?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the
info command
because it could not find the string REVISION. This was not a good
thing!
Is there a better way to obtain the SVN revision number that does not
suffer from this sort of problem?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://ww
e original build behavior?
Although I would be perfectly fine just having a target that allowed
updating those files on demand.
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to su
dependent upon having an up-to-date build, so I'd like to put in a
dependency where a complete build is attempted if we're building the
installer. I tried specifying ALL in the DEPENDS section, but it didn't
like that. Is there a variable available that contains the list of ALL
targets?
Ri
cmake -P, but a quick test revealed that the script does not inherit the
variable environment and the variables I'm working with cannot be easily
passed using -D values on the command line.
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
w the
_CPack_Packages/win64/NSIS/project.nsi
file and the .nsh files can't be located. How can I get the template
source directory included in the search path?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offe
semicolons inserted between the list
elements. I need to have this inserted as a series of lines rather than a
single line. Is there someway to control this substitution? Or as an
alternative, is it possible to convert a list of strings into a single
string with inserted newlines?
Rick
--
Is there a variable that contains the list of components that have had
install() commands issued for them?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake
documentation. We do something similar with our samples. I suspect we can
do this with a custom template that checks the section variables, but it
would be nicer if we could drive this from the cmake files.
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at
command, I get
the following error:
CMake Error at CMakeLists.txt:887 (install):
install Library TARGETS given no DESTINATION!
How can I install just the .dll file, or failing that cause the ARCHIVE
file portion of the install to end up in a bit-bucket so that NSIS never
physically ins
The ubuntu
installer is throwing an error because it expects these files to have more
restrictive permissions of 0644. How can we get these files to the correct
permissions when the package is built?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www
suming the rexximage.exe file will be in the
CMAKE_RUNTIME_OUTPUT_DIRECTORY, which is specified as
${CMAKE_CURRENT_BINARY_DIR}/bin. Is there a more appropriate method
we should be doing to locate this executable that will work using both
the NMake build process and a Visual Studio project?
Rick
--
That was the first thing I tried. I even tried doing this with a freshly
checked-out source tree, and it still wrote all of the files to the root of
the source tree. This was working for me as recently as Tuesday, so I'm
not sure what might have changed.
Rick
On Sat, May 17, 2014 at 1:
ather than in the
current directory? I've tried all sorts of combinations here, but can't
seem to replicate my earlier success at creating the debug and release
subdirectories originally. What's going on here?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic a
t up front without needing to add a bunch of extra conditional
windows-only steps throughout the configuration file.
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake
Figured out the answer on my own. The problem was how I was specifying the
file names on the depends. Once I added the directory to the output file
and used the directory on subsequent dependencies, this started working the
way I expected.
Rick
On Thu, May 8, 2014 at 5:39 PM, Rick McGuire
ed means all
of the subsequent build stages that have a dependency on the rexx.img
file also get activated. Why is this happening and is there anything
I can do to stop this from being generated unconditionally?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check t
cmake to generate an
executable with a .com extension. Has anybody needed to deal with this
issue before?
Rick
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. F
e different
kinds of build working.
Rick
On Thu, May 1, 2014 at 9:09 AM, Nils Gladitz wrote:
> On 01.05.2014 15:04, Rick McGuire wrote:
>
>>
>> With our existing setup, to switch between 32- and 64- bit builds, we
>> only need to change the option specified on the vcvars
on the link command. I tried manually deleting that
option, but the error persisted. What do I need to do for cmake to
generate the correct 64-bit logic...and equally as important, how do we
switch between doing 32-bit and 64-bit builds when needed?
And let me repeat, we do not want to use the Vi
n_dir}
COMMAND ${CMAKE_COMMAND} -E copy_directory ${source_dir}
${destination_dir}
)
Any suggestions?
Thanks very much!
- Rick Gould
r...@transpireinc.com
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.ki
pdate failure to the dashboard.
I haven't found any indication this is a known bug - Has anyone else
seen this problem? Is there a work-around? Or shall I go ahead and
file a bug report?
Details follow.
Thanks,
- Rick Gould
-
Here's the applicable part of our build log. N
rrors associated with these files):Error(s) while acumulating results:
Problem reading source file: /home/rick/myproject/src/mylibrary/tests/tsphostname.cpp line:13
Problem reading source file: /home/rick/myproject/src/mylibrary/tests/tsptime.cpp line:13
Problem reading source file: /home/rick/myprojec
I appears that -Wmost is hard coded in the CFLAGS for XCode
projects. Is there anyway to disable this without change the cmamke
code and re-compiling it?
Rick M
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
28 matches
Mail list logo