Dear experts,
our problem is that cmake sets automatically linking libraries for C,C++ and
with Intel compilers (Fortran,C,C++) we are getting these problems
( first observed here
https://repo.ctcc.no/CDash/viewBuildError.php?buildid=5283 ) :
.
.
.
Linking Fortran executable dirac.x
/people/disk
On 11/09/2011 06:06 PM, EXT-York, Gantry wrote:
> I'm looking for suggestions from someone who has used CTest to report results
> to a dashboard other than CDash.
>
> I'd like to be able to simply type
>
> gmake test TESTOPTS="-report"
>
> then have CTest traverse all the directories and run th
Hi,
I have a CMake-based project which builds several shared libraries and
executables.
There are various run-time dependencies between those shared libraries
and executables.
On Windows, I use Visual Studio for development, so I have CMake-generated .sln
with projects. loaded into the IDE. I bui
But said he was trying to own it in visual studio express.
Mike J
On Friday, November 11, 2011, John Drescher wrote:
>> There should have been a "*.sln" file that you open.?
>>
>
> Not for a "Code Blocks -NMake Makefile" project.
>
> John
>
--
__
I'm getting a Link error on Linux when I use CMake 2.8.6 or 2.8.5. If use
CMake 2.6.3, with the exact same configuration, the link works.
I did a diff on the build.make from 2.8.6 and 2.6.3 and found when I use cmake
2.8.6 On Linux adding headers to ..._EXTERNAL_OBJECTS for executables under
On Fri, Nov 11, 2011 at 11:01 PM, Dan Kegel wrote:
> I have no idea how to make that happen inside the cdt generator. I could
> kludge
> it in the shell script that runs cmake, but then it would break whenever
> the project was updated and cmake rebuilt the project automatically.
OK, the follow
>
> > *To use QtCreator*
> > The consensus is to use the "Code Blocks - NMake Generator". This has
> > generated successfully a .cbp file (Code Block Project, I'm assuming).
> > However, QtCreator seems unaware that this is a project and just opens it
> > as plain text? How do I now open this proje
Am Samstag, 12. November 2011, 00:05:20 schrieb David Doria:
> On Fri, Nov 11, 2011 at 5:56 PM, John Drescher wrote:
> >> There should have been a "*.sln" file that you open.?
> >
> > Not for a "Code Blocks -NMake Makefile" project.
> >
> > John
>
> Ok, I guess I am getting my two threads confu
On Fri, Nov 11, 2011 at 5:56 PM, John Drescher wrote:
>> There should have been a "*.sln" file that you open.?
>>
>
> Not for a "Code Blocks -NMake Makefile" project.
>
> John
Ok, I guess I am getting my two threads confused.
*To use QtCreator*
The consensus is to use the "Code Blocks - NMake Ge
In http://www.cmake.org/pipermail/cmake/2011-November/047250.html
I wrote
"I can't reorganize the source tree on the developers,
so I'm making do by putting the enclosing CMakeLists.txt next to all
the projects:
toplevel/trunk/CMakeLists.txt
which is checked out to
toplevel/CMakeLists.txt
It
> There should have been a "*.sln" file that you open.?
>
Not for a "Code Blocks -NMake Makefile" project.
John
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
It is worse and better.
1: CMake will generate the VS projects and solutions every time it needs to
run. DO NOT EDIT the generated VS projects and solutions. Add the requirements
to the CMake files.
2: If you are on VS2007/VS2008 and you do a "git pull" and then switch to VS
and click build a
There should have been a "*.sln" file that you open.?
___
Mike JacksonPrincipal Software Engineer
BlueQuartz SoftwareDayton, Ohio
mike.jack...@bluequartz.net www.bluequartz.net
On N
I typically work in KDevelop which has CMake support, so if another
developer pushes some new files and changes to the CMakeLists.txt of
my project, I simply 'git pull' the project and then click "Build" and
it knows exactly what to do - it runs CMake and then builds the
project.
However, when wor
> That is the best way I have found to run CMake on Windows when multiple
> Visual Studios are installed. There is a Command Prompt short cut called
> "Visual Studio Command Prompt" that will have all the compiler paths setup
> for you. What I do is launch that command prompt then issue "cmake-g
On Fri, Nov 11, 2011 at 9:42 PM, Alexander Neundorf
wrote:
> So you imported the source project (and the build project), and now svn works
> for the source project ?
Right (I think). The symptom was that the source project would not import.
Now it does, reliably.
> Or does it also work in the b
On Nov 11, 2011, at 4:44 PM, Alexander Neundorf wrote:
> On Friday 11 November 2011, David Doria wrote:
>>> Ok. one more: how exactly did you run cmake ?
>>> From the command line or cmake-gui ?
>>
>> From the CMake-GUI.
>>
>>> Which generator did you choose ?
>>> It should be the "CodeBlocks -
On Friday 11 November 2011, David Doria wrote:
> > Ok. one more: how exactly did you run cmake ?
> > From the command line or cmake-gui ?
>
> From the CMake-GUI.
>
> > Which generator did you choose ?
> > It should be the "CodeBlocks - NMake Makefiles" one.
>
> I had chosen "CodeBlocks - Unix Ma
On Friday 11 November 2011, Dan Kegel wrote:
> On Fri, Nov 11, 2011 at 3:58 PM, Alexander Neundorf
>
> wrote:
> > What did you do ? Can you please explain exactly ? I'd really like to
> > know.
>
> I can't explain my previous problem - must have been stupid user error,
> like being in wrong dire
On 11/11/2011 2:25 PM, Robert Dailey wrote:
Based on this URL:
http://cygwin.com/ml/cygwin/2006-07/msg00376.html
Seems like this happens because I am using windows-style paths in
Cygwin. I don't know how to make it use different paths though.
It is because the cygwin make is broken. Did you tr
UNIX is ON for cygwin based builds. (However, WIN32 is not ON any
longer. It used to be, but the cygwin guys didn't want it that way, so
now WIN32 is OFF.)
Assuming you are in a directory named "CMake" which is the CMake
source tree, you can do the following to produce a cygwin based CMake
(in a r
On Fri, Nov 11, 2011 at 3:58 PM, Alexander Neundorf
wrote:
> What did you do ? Can you please explain exactly ? I'd really like to know.
I can't explain my previous problem - must have been stupid user error,
like being in wrong directory.
- Dan
--
Powered by www.kitware.com
Visit other Kitware
> Ok. one more: how exactly did you run cmake ?
> From the command line or cmake-gui ?
>From the CMake-GUI.
> Which generator did you choose ?
> It should be the "CodeBlocks - NMake Makefiles" one.
I had chosen "CodeBlocks - Unix Makefiles". I just tried again with
"CodeBlocks - NMake Makefiles"
On Fri, Nov 11, 2011 at 3:24 PM, Robert Dailey wrote:
> According to the root CMakeLists.txt in cmake, there is no way to do this on
> Windows. I'll probably have to build it through Cygwin itself, assuming UNIX
> is truthy when using Cygwin.
> # Use curses?
> IF (UNIX)
> # there is a bug
According to the root CMakeLists.txt in cmake, there is no way to do this
on Windows. I'll probably have to build it through Cygwin itself, assuming
UNIX is truthy when using Cygwin.
# Use curses?
IF (UNIX)
# there is a bug in the Syllable libraries which makes linking ccmake
fail, Alex
I'm using Cygwin with the MSVC toolchain and I need ccmake.exe. I can't use
the one from the Cygwin package manager because it's older than the version
I'm using. I'd like to build it myself through Visual Studio like I did
with cmake and cmake-gui if possible. Any help?
-
Robert Dailey
--
On Friday 11 November 2011, David Doria wrote:
> On Fri, Nov 11, 2011 at 12:42 PM, Alexander Neundorf
>
> wrote:
> > On Friday 11 November 2011, David Doria wrote:
> >> >> I think it's true that QtCreator knows how to connect to a CMake
> >> >> build tree generated with the "CodeBlocks - Unix Mak
On Fri, Nov 11, 2011 at 12:42 PM, Alexander Neundorf
wrote:
> On Friday 11 November 2011, David Doria wrote:
>> >> I think it's true that QtCreator knows how to connect to a CMake build
>> >> tree generated with the "CodeBlocks - Unix Makefiles" generator.
>>
>> I tried to use this generator, but
On Friday 11 November 2011, David Doria wrote:
> >> I think it's true that QtCreator knows how to connect to a CMake build
> >> tree generated with the "CodeBlocks - Unix Makefiles" generator.
>
> I tried to use this generator, but I get errors like
> "cmake_c_compiler_env_var is undefined". Shoul
>> I think it's true that QtCreator knows how to connect to a CMake build
>> tree generated with the "CodeBlocks - Unix Makefiles" generator.
I tried to use this generator, but I get errors like
"cmake_c_compiler_env_var is undefined". Shouldn't it find the
compiler for the VS2010Express installat
Do you have a sample bash script I could look at? I'm not sure what
environment variables need to be setup in my Cygwin environment.
Thanks!
-
Robert Dailey
On Thu, Nov 10, 2011 at 10:05 PM, Bill Hoffman wrote:
> On 11/10/2011 5:14 PM, Robert Dailey wrote:
>
> I think my incorrect sub
Based on this URL:
http://cygwin.com/ml/cygwin/2006-07/msg00376.html
Seems like this happens because I am using windows-style paths in Cygwin. I
don't know how to make it use different paths though.
-
Robert Dailey
On Fri, Nov 11, 2011 at 1:19 PM, Robert Dailey wrote:
> At line 25 in
At line 25 in the depend.make file in question, I have this:
common/exchange/gdexchsrvcommon/CMakeFiles/gdwincommon.dir/gdcomhelpers.cpp.obj:
C:/Program\ Files/Microsoft\ SDKs/Windows/v6.0A/Include/SCardErr.h
-
Robert Dailey
On Fri, Nov 11, 2011 at 1:17 PM, Robert Dailey wrote:
> I ha
I have been generating for Visual Studio, but I decided to try setting up
my Cygwin environment to point to the MSVC tool chain. So far it's worked
wonderfully, but one of my targets is failing and I don't understand
Makefiles very well so I have no idea what the problem is. Note that I'm
doing an
On Friday 11 November 2011, David Cole wrote:
> On Fri, Nov 11, 2011 at 1:08 PM, David Doria wrote:
> > I saw a discussion about this back in March, but I didn't see any
> > conclusions/resolutions. Is there a way to generate a QtCreator
> > project using CMake? I tried the CMake support that was
On Fri, Nov 11, 2011 at 1:08 PM, David Doria wrote:
> I saw a discussion about this back in March, but I didn't see any
> conclusions/resolutions. Is there a way to generate a QtCreator
> project using CMake? I tried the CMake support that was built into
> QtCreator itself, but it seems very awkwa
I saw a discussion about this back in March, but I didn't see any
conclusions/resolutions. Is there a way to generate a QtCreator
project using CMake? I tried the CMake support that was built into
QtCreator itself, but it seems very awkward (you couldn't view/set
variables, etc).
Thanks,
David
--
Am Freitag, 11. November 2011, 15:55:12 schrieb Stefan Monnier:
> > According to http://caml.inria.fr/pub/docs/manual-ocaml/manual022.html,
> > it does:
> > -o exec-file
> >
> > Specify the name of the output file produced by the compiler. The
> >
> > default output name is a.out under Unix a
Am Freitag, 11. November 2011, 17:41:34 schrieb David Cole:
> You just need to install a PlatformSDK to go with VS 2010 Express.
> Search the mailing list for prior discussions of this fact.
Last time I tried, VS10Express included the PlatformSDK.
HS
--
Powered by www.kitware.com
Visit other Ki
On 11 November 2011 16:36, David Doria wrote:
> I am using CMake 2.8.6 and am hoping to generate a project for VS2010
> Express. Which generator should I use? I tried Visual Studio 10, but
> when I "configure" I get all kinds of errors about the compiler not
> working. I can try to transcribe thes
You just need to install a PlatformSDK to go with VS 2010 Express.
Search the mailing list for prior discussions of this fact.
On Fri, Nov 11, 2011 at 11:36 AM, David Doria wrote:
> I am using CMake 2.8.6 and am hoping to generate a project for VS2010
> Express. Which generator should I use? I t
Thanks.
You saved the day (again).
Works perfectly.
On Nov 11, 2011, at 5:22 PM, David Cole wrote:
> On Fri, Nov 11, 2011 at 11:12 AM, Daniel Dekkers
> wrote:
>> Hi,
>>
>> We are building a lib and an example app in Xcode (4.2) targeting iOS (5.0).
>>
>> The top-level CMakeLists.txt recurses
I am using CMake 2.8.6 and am hoping to generate a project for VS2010
Express. Which generator should I use? I tried Visual Studio 10, but
when I "configure" I get all kinds of errors about the compiler not
working. I can try to transcribe these if necessary, but I thought
there might be an easier
On Fri, Nov 11, 2011 at 11:12 AM, Daniel Dekkers wrote:
> Hi,
>
> We are building a lib and an example app in Xcode (4.2) targeting iOS (5.0).
>
> The top-level CMakeLists.txt recurses into lib and example:
>
> PROJECT(Suite)
> ADD_SUBDIRECTORY(MyLibrary)
> ADD_SUBDIRECTORY(MyExample)
>
> The lib
Hi,
We are building a lib and an example app in Xcode (4.2) targeting iOS (5.0).
The top-level CMakeLists.txt recurses into lib and example:
PROJECT(Suite)
ADD_SUBDIRECTORY(MyLibrary)
ADD_SUBDIRECTORY(MyExample)
The lib is built in the traditional way…
PROJECT(MyLib)
…
ADD_LIBRARY( ${MYLIB_SO
On Thu, Nov 10, 2011 at 4:41 PM, EXT-York, Gantry
wrote:
> If I'm in a traversed subdirectory, is there a different variable other than
> ${CMAKE_CURRENT_SOURCE_DIR} that I should be using?
>
> This doesn't seem to work.
>
>
> Gantry York
> Chandler, Arizona
>
>
>
>
> -Original Message-
>
On Thu, Nov 10, 2011 at 4:33 PM, EXT-York, Gantry
wrote:
> OK, so if I'm trying to add a test do I just
>
> add_executable( run_main.pl IMPORTED )
> set_property(
> TARGET test_script1
> PROPERTY IMPORTED_LOCATION "${CMAKE_CURRENT_SOURCE_DIR}/run_main.pl"
> )
> add_test( test1 run_main.pl)
>
On Friday 11 November 2011, Dan Kegel wrote:
> On Thu, Nov 10, 2011 at 2:32 PM, Dan Kegel wrote:
> > http://www.cmake.org/Wiki/Eclipse_CDT4_Generator
> > says the cdt generator should work with subclipse if you set
> > -DECLIPSE_CDT4_GENERATE_SOURCE_PROJECT=TRUE
> > on the commandline when runnin
On 11 November 2011 13:54, Niels Dekker - address until 2014
wrote:
>>> Update: I think users can work around this issue (#12570, empty
>>> property pages in VS10), by having the directory where to build the
>>> binaries on a separate drive (different from the drive that has the
>>> source files).
In order to work around
http://public.kitware.com/Bug/view.php?id=12570 I think it should be
sufficient to have a different drive *letter* when specifying where
to build the binaries than the drive letter(s) of the path names of
the source files.
John Drescher wrote:
You could also probably use
>> I'm trying to use cmake for a project using OCaml, so I'm trying to add
>> support for a new language.
> Just in case you weren't aware of that.
> There has been [several] discussions on the ML
> in the past concerning CMake OCaml support at least this one:
> http://www.cmake.org/pipermail/cmak
> According to http://caml.inria.fr/pub/docs/manual-ocaml/manual022.html, it
> does:
> -o exec-file
> Specify the name of the output file produced by the compiler. The
> default output name is a.out under Unix and camlprog.exe under Windows. If
This manpage describes all kinds of uses and in p
Ok thanks for your quick answers! It works perfectly now!
Why don't we have just one variables for the library?
With set_target_properties, we can define for each library the path.
Romain
Le 11/11/2011 15:38, Andreas Pakulat a écrit :
On 11.11.11 15:18:05, Romain LEGUAY wrote:
Hello everyon
On 11.11.11 15:18:05, Romain LEGUAY wrote:
> Hello everyone!
> First, I need to thank you all the CMake developers for their
> awesome work!!!
>
> I try to build a static and a shared libraries. I set the
> LIBRARY_OUTPUT_DIRECTORY for each library target like this:
See the documentation for the
On 11/11/2011 03:18 PM, Romain LEGUAY wrote:
> Hello everyone!
> First, I need to thank you all the CMake developers for their awesome
> work!!!
>
> I try to build a static and a shared libraries. I set the
> LIBRARY_OUTPUT_DIRECTORY for each library target like this:
>
> set_target_properties(${
Hello everyone!
First, I need to thank you all the CMake developers for their awesome
work!!!
I try to build a static and a shared libraries. I set the
LIBRARY_OUTPUT_DIRECTORY for each library target like this:
set_target_properties(${sharedLib} PROPERTIES
LIBRARY_OUTPUT_DIRECTORY
${PR
> In order to work around http://public.kitware.com/Bug/view.php?id=12570 I
> think it should be sufficient to have a different drive *letter* when
> specifying where to build the binaries than the drive letter(s) of the path
> names of the source files. So I guess one might work around this issue
Update: I think users can work around this issue (#12570, empty
property pages in VS10), by having the directory where to build the
binaries on a separate drive (different from the drive that has the
source files).
Mateusz Loskot wrote:
Separate drive may not be an option for some/many.
I, for
Separate drive may not be an option for some/many.
I, for instance, don't use partitions, but I use
CMakeas as main builder for my projects.
So, I feel the pain of reloading, thus
It's easier/quicker for me to close solution, rerun CMake,
reopen solution.
--
Mateusz Łoskot
Sent from my mobile (ex
Update: I think users can work around this issue (#12570, empty property
pages in VS10), by having the directory where to build the binaries on a
separate drive (different from the drive that has the source files).
Please let me know if you think that's not a good idea! Or if it does not
work
On 11/11/2011 04:13 AM, Michael Hertling wrote:
On 11/10/2011 11:22 PM, Eric Noulard wrote:
If this is the case then it is a "GL/glxproto.h" design mistake
not CMake mistake.
Absolutely, try to compile the following program by hand; it's
the same the CHECK_INCLUDE_FILE() macro tries to compile,
Hi,
> > it reaches the linker. I can't simply add WIN32 to
> add_executable()
> > because I want debug builds to use the console sub-system
> and release
> > builds to use the windows subsystem. I have three questions:
I don't have a solution in cmake, but I worked around this using code fr
62 matches
Mail list logo
