2011/1/11 Andreas Schneider :
> On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
>> Hi Andreas,
>
> Hi Andrea,
>
>> I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
>> me very happy to know that someone are working to integrate Java in
>> CMake. My question is: sho
> On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
> > Hi Andreas,
>
> Hi Andrea,
>
> > I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
> > me very happy to know that someone are working to integrate Java in
> > CMake. My question is: shouldn't Ant be enough? Or
On Tue, Jan 11, 2011 at 4:21 PM, Crni Gorac wrote:
> On Tue, Jan 11, 2011 at 6:22 PM, David Cole
> wrote:
> > On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
> > wrote:
> >>
> >> This is wonderful and I am making progress but I have a few more
> >> questions. Assume I am using CMake 2.8.3 (as
Am Dienstag, 11. Januar 2011, 11:20:06 schrieb David Cole:
> Yes... this confused me when I first encountered it as well.
>
> TRY_COMPILE is misnamed in CMake.
>
> In functionality, it's actually a TRY_LINK operation.
Update the doc?
Eike
signature.asc
Description: This is a digitally signed m
On Tue, Jan 11, 2011 at 6:22 PM, David Cole wrote:
> On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson
> wrote:
>>
>> This is wonderful and I am making progress but I have a few more
>> questions. Assume I am using CMake 2.8.3 (as it will become the
>> requirement).
>>
>> For external Dylibs and
Hello,
My experience with CMake programming is evolving. I try to update some scripts
which were published with the feature request "Add simple CMake build files".
https://sourceforge.net/apps/trac/cppcheck/ticket/1092#comment:5
A concern that I try to tackle as a next step for this software p
Am Dienstag, 11. Januar 2011 schrub Eric Noulard:
[many great ideas how to solve my issue]
Thank you very much folks. I guess I will find something with the pointers you
gave me. :-)
> Current source packaging is more or less a hack.
> Useful hack, but a hack.
Better than nothing I guess.
si
Hi,
with the new external project support in CMake it is very easy to build
complex projects in one run, but it is still complicated to resolve the
different library paths on windows. There is a bug in the Cmake
bugtracker describing the problem very well, and as somebody pointed out
it also
Thanks for the help, David and and Fraser! I have it working.
On Tue, Jan 11, 2011 at 4:33 AM, David Cole wrote:
> Thanks, Fraser. Of course...
>
> If you need to escape a backslash such that the regular expression itself
> contains a backslash at a certain point, then you need to double it up. F
On Tue, Jan 11, 2011 at 12:08 PM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> This is wonderful and I am making progress but I have a few more questions.
> Assume I am using CMake 2.8.3 (as it will become the requirement).
>
> For external Dylibs and frameworks that my project depends
This is wonderful and I am making progress but I have a few more questions.
Assume I am using CMake 2.8.3 (as it will become the requirement).
For external Dylibs and frameworks that my project depends on will the new way
that bundle utilities work still copy the frameworks (like Qt frameworks
Dear CMake experts,
I'm facing the following problem. I have a project with many
subdirectories, all at the same hierarchical level:
/my/project/path/CMakeLists.txt
/my/project/path/A - include
|- src
|- CMakeLists.txt
/my/project/path/B - include
On Tuesday 11 January 2011 16:01:14 Andrea Galeazzi wrote:
> Hi Andreas,
Hi Andrea,
> I'm a dyed-in-the-wool Java developer (and also Fedora user) so it makes
> me very happy to know that someone are working to integrate Java in
> CMake. My question is: shouldn't Ant be enough? Or better, Could
>
Yes... this confused me when I first encountered it as well.
TRY_COMPILE is misnamed in CMake.
In functionality, it's actually a TRY_LINK operation.
On Tue, Jan 11, 2011 at 10:59 AM, Marcel Loose wrote:
> Hi David,
>
> I guess you're right. Further playing with CheckCXXSourceCompiles and
> in
On Tue, Jan 11, 2011 at 10:31 AM, Michael Jackson <
mike.jack...@bluequartz.net> wrote:
> Thanks for the explanation David it really helps to narrow down what might
> be going on. Couple of comments. Starting fresh this morning everything
> seems to be working correctly after simply deleting the b
2011/1/11 Michael Hertling :
> On 01/11/2011 09:48 AM, Eric Noulard wrote:
[...]
>> The fact is CPack doesn't know much about "source package" and
>> in fact it package source using the CPACK_INSTALLED_DIRECTORIES directory
>> list.
>> (look at the generated CPackSourceConfig.cmake)
>>
>> I think
Hi David,
I guess you're right. Further playing with CheckCXXSourceCompiles and
investigating the generated CMakeLists.txt file led me to the conclusion
that the link step is indeed also performed. I was led astray by the
name of the command and my notion that it wraps TRY_COMPILE. Also my
backgro
Thanks for the explanation David it really helps to narrow down what might be
going on. Couple of comments. Starting fresh this morning everything seems to
be working correctly after simply deleting the build folder and starting over.
So maybe I had a stale cmake variable floating around.
Also
On 01/11/2011 09:48 AM, Eric Noulard wrote:
> 2011/1/11 Michael Hertling :
>> On 01/11/2011 12:55 AM, Tobias Ellinghaus wrote:
>>>
>>> Because some information (like latest git commit as version string) is no
>>> longer available when using a source package. Of course I can put the
>>> generated fi
Do you get different results if you use CMake from git 'master' or 'next' ??
(Or CMake 2.8.2...?)
In 2.8.3, there was a change introduced that caused problems in *some*
projects. I suspect your project is one of them.
This commit:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c2895f48a4e79af
Andreas Schneider ha scritto:
Hello CMake,
my name is Andreas Schneider and I'm working for Red Hat. At the end of last
year I've worked on Dogtag PKI [1]. The Dogtag Certificate System [2] is an
enterprise-class open source Certificate Authority.
The project is written in serveral different
Hi,
probably it could sound a weird question: has anyone ever try to
generate a VS2010 solution with a different toolchain like gcc? In your
opinion is it a possible goal to achieve or the differences between MSVC
and GCC are so big that it's actual impossible?
Cheers
At Tue, 11 Jan 2011 12:40:03 + (GMT),
Carlos Lopez Gonzalez wrote:
>
> Hi!
> I'd like to use cmake on our project (Synfig - http://synfig.org)
> Currently it uses autotools and pkconfig to prepare the code to the build and
> install processes. It is a C++/gtkmm application. Currently it build
On 12/15/2010 11:10 AM, Mario Rodríguez wrote:
> Intel Fortran Composer 12.0 32b
Not currently supported:
http://www.cmake.org/Bug/view.php?id=11517
Sorry,
-Brad
Dear all,
I have the same problem as described before: I use Visual Studio 2010 and
also Intel Fortran compiler 12. This gives
Hi!
I'd like to use cmake on our project (Synfig - http://synfig.org)
Currently it uses autotools and pkconfig to prepare the code to the build and
install processes. It is a C++/gtkmm application. Currently it builds fine on
linux, builds with lots of hacking on windows under cgwin and nobody ma
Doesn't CheckCXXSourceCompiles link?
I think there's no way to avoid the link in a try_compile...
On Tue, Jan 11, 2011 at 5:49 AM, Marcel Loose wrote:
> Hi all,
>
> I was wondering how I can check whether I can successfully compile and
> link an executable, without actually running it. CheckCX
Thanks, Fraser. Of course...
If you need to escape a backslash such that the regular expression itself
contains a backslash at a certain point, then you need to double it up. For
example to match the backslash character itself, you need to use "[\\]", but
to encode other escape chars directly that
Hello CMake,
my name is Andreas Schneider and I'm working for Red Hat. At the end of last
year I've worked on Dogtag PKI [1]. The Dogtag Certificate System [2] is an
enterprise-class open source Certificate Authority.
The project is written in serveral different laguages (C, C++ and Java), so
Zitat von "Thomas Petazzoni" :
On Tue, 11 Jan 2011 01:42:47 +0100
Michael Hertling wrote:
Since CMake prefers to specify libraries by path instead of using
-l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
command, IMO.
Sorry to jump into the discussion, but I'm having a
Hi all,
I was wondering how I can check whether I can successfully compile and
link an executable, without actually running it. CheckCXXSourceCompiles
checks whether I can compile the code, however linking could still fail.
CheckCXXSourceRuns OTOH also tries to run the executable, which causes
pro
On 11.01.11 10:27:02, Thomas Petazzoni wrote:
> Hello,
>
> On Tue, 11 Jan 2011 01:42:47 +0100
> Michael Hertling wrote:
>
> > Since CMake prefers to specify libraries by path instead of using
> > -l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
> > command, IMO.
>
> Sorry t
Hello,
On Tue, 11 Jan 2011 01:42:47 +0100
Michael Hertling wrote:
> Since CMake prefers to specify libraries by path instead of using
> -l/-L or the like, there's usually no need for the LINK_DIRECTORIES()
> command, IMO.
Sorry to jump into the discussion, but I'm having a problem that I
think
> Manu,
> please maintain the discussion on the mailing list as these is a general issue
Sure, sorry (actually I replied to your PM, I have not seen it did not
contain a cc: to the ML)
> if you are cross compiling, the target is not cygwin, so CYGWIN is not
> defined.
Ok, understood.
> However
> On 01/10/2011 06:24 PM, Andrea Galeazzi wrote:
>> I've got a main project which relies on several sub-library projects, so
>> the main CMakeLists.txt
>> add_subdirectory("W:/Omega/Kernel"
>> "${CMAKE_CURRENT_BINARY_DIR}/myLib1")
>> ...
>> and then I also specify the directory where all li
On Mon, Jan 10, 2011 at 6:55 PM, Emmanuel Blot wrote:
> On Mon, Jan 10, 2011 at 5:56 PM, marco atzeri wrote:
>> I don't understand why you find and empty definition
>
> Well, it seems that CYGWIN is not defined:
>
> MESSAGE (STATUS "CYGWIN: ${CYGWIN}")
> MESSAGE (STATUS "Suffix: ${CMAKE_EXECUTA
2011/1/11 Michael Hertling :
> On 01/11/2011 12:55 AM, Tobias Ellinghaus wrote:
>>
>> Because some information (like latest git commit as version string) is no
>> longer available when using a source package. Of course I can put the
>> generated files into the source tree, but that's kind of agains
2011/1/11 Tobias Ellinghaus :
> Am Montag, 10. Januar 2011 schrub Eric Noulard:
>
>> > which would at least allow to copy the files into
>> > CMAKE_CURRENT_SOURCE_DIR.
>>
>> You may generate those file (with configure_file) inside your source tree
>> and the generated file will be packaged by "pack
37 matches
Mail list logo
