Anyone? Any suggestions would be appreciated.
Petr
On Mon, Sep 24, 2012 at 5:16 PM, Petr Kmoch wrote:
> Hi all,
>
> I seem to have a problem when using add_test(... CONFIGURATIONS ...) and
> running 'make test' on Linux. It's skipping the test.
>
> The CMakeLists.txt contains:
> #...
> enable_t
Hi,
I was able to build win64 executable on my 32-bit Windows.
First, I had to make the "full installation" of VS 2008 (the "default
installation" did not provide the win64 compiler in my case). Then, I
had to select the "Visual Studio 9 2008 Win64" generator in CMake. And
the project built corre
On Mon, Oct 1, 2012 at 4:35 PM, Arindam Mukherjee
wrote:
> Hi,
>
> I have a Windows XP build setup with Visual Studio 2008 SP1 and
> Windows SDK 6. I have set up a CMake project for a source base that is
> built on Linux, Solaris, AIX and Windows. So far I have managed to get
> the Windows 32-bit
See USERFILE_COMMAND_ARGUMENTS_DEBUG in this Stack Overflow question &
answer:
http://stackoverflow.com/questions/1005901/how-to-set-path-environment-variable-using-cmake-and-visual-studio-to-run-test
Also, be sure to read all the comments, too. There are helpful tips in
there about what version
Hello,
I am wondering if there is a target property for executable to set a command
line argument. I did a bit of googling but I might have missed it.
Something like:
add_executable (myProgram main.cpp)
set_target_properties (myProgram COMMAND_LINE_ARGUMENTS "--verbose --run")
This would set
Any ideas?
Laszlo
On Thu, Sep 27, 2012 at 9:22 PM, Laszlo Papp wrote:
> Seems those variables are empty:
>
> -- Looking for _POSIX_TIMERS - found
> CMAKE_PREFIX_PATH:
> CMAKE_MODULE_PATH:
> CMake Error at
> /usr/share/apps/cmake/modules/FindPackageHandleStandardArgs.cmake:198
> (MESSAGE):
> D
Also, if it's a Qt app, look into the relatively new (in 2.8.7 and later, I
think) module "DeployQt4" [
http://cmake.org/cmake/help/v2.8.9/cmake.html#module:DeployQt4 ] which is
based on BundleUtilities.
Here's a blog post about using it:
http://mikemcquaid.com/2012/01/04/deploying-qt-applications
Look into "BundleUtilities" and the add_executable with MACOSX_BUNDLE argument.
BundleUtilities implicitly relies on the .app bundle structure already being in
place. I have a Shell script that runs before BundleUtilities to setup some
additional resource movement (icons, qt.conf...). I do all
