Thankyou Thomas, it works now... Another issue I was faced with the first
script is, it assumes that the dlls are in the lib folder of Qt (I think
you build qt from source). I have downloaded the prebuilt Qt library, in
that the dlls are in the bin folder. I modified the macro you have given,
as be
Hi all; I'm tring to build cmake using a cross-compiler environment so
cmake itself will run on a different platform.
It's working well, except that ccmake is not getting compiled (neither
is cmake-gui but that's OK). I do have curses libraries installed and
other curses programs are built and ru
Hello John,
I made some generic scripts to answer has those kind of problem. There
is an example in the folder Examples/FrameworkTest.
You can find the scripts on GitHub:
https://github.com/Athius/FrameworkCMakeToolkit
I hope this is helpful.
Best regards,
Romain
Le 18/04/13 05:38, John
Normally when you find the Qt4 package it selects some defaults libraries (and
the QT_USE_FILE). But you have to specify some extra modules you may need
before including the QT_USE_FILE. The QT_USE_FILE defines the dependencies and
includes the folders you need.
For example I have:
find_packag
Kitware will be holding a developers training course on May 27, 2013 in
Lyon, France. This one-day course will cover CMake, CTest, CPack and CDash
Please visit our website for more information and registration details
(early registration ends May 6) at:
http://www.kitware.com/products/protr
I assume that this is the recommended approach.
I tried to use the script you have provided, the call GetQtDLLs(DEBUG_DLLS
RELEASE_DLLS) is not populating any of the variables (DEBUG_DLLS or
RELEASE_DLLS) with qt dll names. I am new to cmake, Am I missing something?
Thanks,
Lloyd
On Thu, Apr
Hi Lloyd,
Personally I copy the DLLs to the VS folder (so that the program can be run
from visual studio) using the following script.
It looks more complicated than it is.
A macro is available to several of my projects to select which Qt module they
use and create a list of dlls to copy.
Then I
Hi,
On Thursday, 18. April 2013, 09:02:13, 中野佑香 wrote:
> $ tar -xvzf gromacs-4.6.1.tar.gz
> $ cd gromacs-4.6.1
> $ mkdir build
> $ cd build
> $ cmake ..
>
> However, I got an error.
> ---
> CMake Error: The source directory
>
Hi,
I was successful in creating and building a project using CMake on Windows
(Visual Studio). After the build when I try to run the application it
throws an error asking for the dlls of Qt (I know it is a common case in
Windows, usually we do copy the dlls to debug/release folder where the exe
r
Hello John,
On Wednesday 17 April 2013 23:38:36 John Gallagher wrote:
> 3. (This one is unclear.) Somehow build proj1 before configuring proj2, and
> point proj2 at proj1's build directory so it can find Proj1Config.cmake.
> This seems fragile at best (prefix, RPATH, etc issues).
when using Exter
Hello John,
Maybe I am missing something but can't you do something like this in proj2s
cmakelists.txt?
if( TARGET proj1 )
list_of_libraries_to_link_against( ${ list_of_libraries_to_link_against}
proj1 )
else( TARGET proj1 )
find( proj1 required )
list_of_libraries_to_link_against( ${ li
Hi. I'm trying to build a build with cmake-2.8.10.2-linux for
'gromacs-4.6.1' as the build target.
First,
I extracted gromacs-4.6.1.tar.gz and, create a new folder; build inside
the extracted folder.
Then, inside build folder, I configured using CMake.
$ tar -xvzf gromacs-4.6.1.tar.gz
$ cd groma
12 matches
Mail list logo