[CMake] custom build

2016-07-29 Thread Lev
Dear cmake users, Could you please help me how to make cmake to produce a generic build system? What I want to do is running simple shell command on files. Namely, I want to generate sqlite database from a sql file. It all works from the command line, I just can't figure out how to make cmake

Re: [CMake] custom build

2016-07-29 Thread Lev
ing plain "make" here. Yes, I considered that solution. Then I have to make the upper level CMakeLists.txt/build system to run "make" in that directory, and somehow make my global variables visible in that Makefile. Seems to be harder than hacking the CMakeLists.txt. And, I want to hav

Re: [CMake] custom build

2016-07-29 Thread Lev
On Fri, 29 Jul 2016 08:50:13 -0400 Guillaume Dumont wrote: > add_custom_command(OUTPUT foo.sqlite > MAIN_DEPENDENCY > foo.sql COMMAND "cat foo.sql | > sqlite3 -batch foo.sqlite") > > add_custom_target(foo_sqlite >

[CMake] symlink copy

2016-08-08 Thread Lev
All, I have a data files to install that contains symbolic link. When I install first time, everything is okay. However, if I reinstall I get this error: file INSTALL cannot duplicate symlink Is there any workaround to squelch this error? Thank you, Lev -- 73 de HA5OGL Op.: Levente

[CMake] set the compiler

2016-09-23 Thread Lev
ot;) endif () cmake complains, that gcc is not in my path, but it is. leva@jive:~$ which gcc /usr/bin/gcc I haven't tried it on the FreeBSD yet. Any solutions for this? Thanks, Lev -- 73 de HA5OGL Op.: Levente -- Powered by www.kitware.com Please keep messages on-topic and check the

[CMake] cmake vs. Python 3.4

2016-12-23 Thread Lev
Hi list, I have this: FIND_PACKAGE(PythonInterp) and cmake finds this: -- Found PythonInterp: /usr/bin/python (found version "2.7.9") However, 3.4 is also installed. How can I specify to find 3.4? If I say: set(Python_ADDITIONAL_VERSIONS 3.4) FIND_PACKAGE(PythonInterp 3 REQUIRED) still no

Re: [CMake] cmake vs. Python 3.4

2016-12-23 Thread Lev
On Fri, 23 Dec 2016 12:53:30 -0800 (PST) "Alan W. Irwin" wrote: > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. Ok. Thanks both of you. Merry XMAS,