Olaf,
>>> Why?
>>> I'm still waiting for someone to post a reason of why a decorated
>>> name is a problem for them.
>>> Also waiting on an answer to the code duplication issue.
Perhaps you should write a proposal that takes care of details, like how you
would like to see this decorated. Then wr
I would like to see full support for multiple components in cpack.
On Tuesday 06 Jul 2010 12:01:17 am David Cole wrote:
> Hi all,
>
> Now that we have released CMake 2.8.2 last Monday, and we have switched to
> this new workflow using branches in the git repository, *now* would be a
> great time
I really wish you guys would have had this conversation on a separate thread
dedicated to the topic. (Oh wait, there already was one...)
Please take it to another thread, and leave this one as "Bug fix requests
for the *next* release of CMake..."
Thanks,
David
On Thu, Jul 29, 2010 at 7:01 PM,
On Fri, Jul 30, 2010 at 1:00 AM, Clinton Stimpson wrote:
>>
>> Why?
>> I'm still waiting for someone to post a reason of why a decorated name
>> is a problem for them.
>> Also waiting on an answer to the code duplication issue.
>>
>
> An automatic naming scheme could break existing applications th
>
> Why?
> I'm still waiting for someone to post a reason of why a decorated name
> is a problem for them.
> Also waiting on an answer to the code duplication issue.
>
An automatic naming scheme could break existing applications that search for
plugins based on their names.
Some of those develo
On Fri, Jul 30, 2010 at 12:28 AM, Michael Jackson
wrote:
>
> On Jul 29, 2010, at 6:24 PM, Olaf van der Spek wrote:
>
>>> As it is now CMake offers
>>> the functionality you want.
>>
>> It doesn't. I'd like CMake to generate libs with unique names and it
>> doesn't...
>
> It DOES. The cmake code ha
Well luckily there are a whole slew of projects to take a look at.
HDF5 is one. CMake, VTK, ITK, ParaView are some others. Basically you
have a .cmake file that runs all the tests like looking for headers,
structs, functions and stuff like that. Each result is put into a
cmake variable. The
I'm now at the point in writing CMake logic where I need to handle the
config.h.in situation, and either have missed the autoheader
equivalent functionality in CMake or it doesn't exist yet. Can
anybody point me to the "right" approach to this? I have so-far
found:
The #cmakedefine mechanism and
On Fri, Jul 30, 2010 at 12:16 AM, Michael Jackson
wrote:
> I am saying that in the past 10 years of programming I found that there
> is NO standard, even within an Operating System itself. Some projects like a
> combined build of debug and release libraries with a "d" suffix on ALL
> platforms
On Fri, Jul 30, 2010 at 12:18 AM, Michael Wild wrote:
> Just enable it, it' so simple.
What's the name of the switch I have to enable?
Olaf
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/o
On 30.07.2010, at 00:07, Olaf van der Spek wrote:
> On Fri, Jul 30, 2010 at 12:04 AM, Michael Jackson
> wrote:
>> Because as a library developer YOU are responsible for making sure your
>> library integrates well with the operating system you intend to deploy on
>> it. Each Operating System
I am saying that in the past 10 years of programming I found that
there is NO standard, even within an Operating System itself. Some
projects like a combined build of debug and release libraries with a
"d" suffix on ALL platforms (Qt) even though OS X would have then put
"_debug". Anoth
On Fri, Jul 30, 2010 at 12:04 AM, Michael Jackson
wrote:
> Because as a library developer YOU are responsible for making sure your
> library integrates well with the operating system you intend to deploy on
> it. Each Operating System has rules according to Person1, Person2,
> Person3 PersonN.
On Jul 29, 2010, at 6:01 PM, Olaf van der Spek wrote:
Everything is a big word. Of course I disagree with you. Ever heard of
abstractions? They're there so one doesn't have to bother with all the
details.
With CMake, I don't have to think about how to build stuff on tons of
different platforms,
On Thu, Jul 29, 2010 at 11:54 PM, Michael Wild wrote:
> If CMake made the choice, somebody (i.e. exactly ONE person) would be a happy
> camper, all the others would have froth in front of their mouths...
Why?
> It is trivial to add the decoration yourself, if you must wrap add_executable
> and
On Thu, Jul 29, 2010 at 11:45 PM, J Decker wrote:
> On Thu, Jul 29, 2010 at 2:22 PM, Olaf van der Spek
> wrote:
>> On Thu, Jul 29, 2010 at 11:13 PM, Michael Wild wrote:
>>> The problem is that there IS NO CONVENTION on name decoration.
>>
>> Why is that a problem?
>
> well that any convention t
On 29. Jul, 2010, at 23:22 , Olaf van der Spek wrote:
> On Thu, Jul 29, 2010 at 11:13 PM, Michael Wild wrote:
>> The problem is that there IS NO CONVENTION on name decoration.
>
> Why is that a problem?
If CMake made the choice, somebody (i.e. exactly ONE person) would be a happy
camper, all
On 7/29/10 10:10 AM, lokmane.abbas-turki wrote:
I am a beginner on creating Visual projects with CMake for Cuda applications. I
use the following CMakeLists
cmake_minimum_required(VERSION 2.8)
PROJECT(FermeHedge)
#Searching CUDA
FIND_PACKAGE(CUDA)
OK, this line is good, but...
#Include t
On Thu, Jul 29, 2010 at 2:22 PM, Olaf van der Spek wrote:
> On Thu, Jul 29, 2010 at 11:13 PM, Michael Wild wrote:
>> The problem is that there IS NO CONVENTION on name decoration.
>
> Why is that a problem?
well that any convention that YOU want, since there is no standard
outside of what YOU de
Michael Wild writes:
>> This is quoting hell. Back to configure_file.
>
> What's wrong with my solution? Doesn't even require a custom command...
It is more complex than configure_file, although it has the advantage of
not requiring a .in file to configure. As this code is suppossed to be
unders
On Thu, Jul 29, 2010 at 11:13 PM, Michael Wild wrote:
> The problem is that there IS NO CONVENTION on name decoration.
Why is that a problem?
> And yes, especially as a library developer you have to be aware of things.
Why?
Olaf
___
Powered by www.ki
On 29. Jul, 2010, at 19:55 , Óscar Fuentes wrote:
> Óscar Fuentes writes:
>
>> Andreas Pakulat writes:
>>
>> [snip]
>>
>>> add_custom_command( OUTPUT build.h
>>>COMMAND cmake -E echo \"\#define FOO \\"bar\\"\"
>>> >build.h )
>>
>> Well, it even makes sense, although it
On 29. Jul, 2010, at 19:26 , Olaf van der Spek wrote:
> On Thu, Jul 29, 2010 at 6:59 PM, Verweij, Arjen
> wrote:
>>> I'd like to see those fixed:
>>> http://public.kitware.com/Bug/view.php?id=11030
>>
>> That one is closed.
>
> Yes, unfortunately. I don't agree with that decision.
>
> Olaf
On Jul 28, 2010, at 6:34 AM, Brad King wrote:
> I'm interested in seeing a solution to this problem. Let's
> discuss the design here first though. What interface do you
> propose?
We're not quite at the point where we are committed to CMake yet. We're still
evaluating several build systems, bu
-Original Message-
From: John Drescher [mailto:dresche...@gmail.com]
Sent: 29 July 2010 21:35
To: Hicham Mouline; CMake mailing list
Subject: Re: [CMake] FindQt4 QT_LIBRARIES
> It does crash currently with release libs for relwithdebingfo config. If I
> link against debug libs, it doesn't
> It does crash currently with release libs for relwithdebingfo config. If I
> link against debug libs, it doesn't crash.
> The question is: when config is relwithdebingfo, how can I get
> TARGET_LINK_LIBRARIES to pick the debug version of the libs from
> QT_LIBRARIES?
>
I use Qt release libs with
>>> Hello,I have looked at FindQt4.cmake module for 2.8.2, but I can't find
the code that sets the QT_LIBRARIES variable.Could someone point that
out?Regards
>
>>It's in UseQt4.cmake.
>
>>HTH
>
>>Michael
>
> I am now trying to link against QT debug libariries in the RelWithDebInfo
cmake configuati
>>> Hello,I have looked at FindQt4.cmake module for 2.8.2, but I can't find
>>> the code that sets the QT_LIBRARIES variable.Could someone point that
>>> out?Regards
>
>>It's in UseQt4.cmake.
>
>>HTH
>
>>Michael
>
> I am now trying to link against QT debug libariries in the RelWithDebInfo
> cma
>On 29. Jul, 2010, at 10:47 , Hicham Mouline wrote:
>> Hello,I have looked at FindQt4.cmake module for 2.8.2, but I can't find the
>> code that sets the QT_LIBRARIES variable.Could someone point that out?Regards
>It's in UseQt4.cmake.
>HTH
>Michael
I am now trying to link against QT debug li
Óscar Fuentes writes:
> Andreas Pakulat writes:
>
> [snip]
>
>> add_custom_command( OUTPUT build.h
>> COMMAND cmake -E echo \"\#define FOO \\"bar\\"\"
>> >build.h )
>
> Well, it even makes sense, although it is not immediately
> obvious. Thanks!
I spoke too soo. This comman
On Thu, Jul 29, 2010 at 6:59 PM, Verweij, Arjen wrote:
>>I'd like to see those fixed:
>>http://public.kitware.com/Bug/view.php?id=11030
>
> That one is closed.
Yes, unfortunately. I don't agree with that decision.
Olaf
___
Powered by www.kitware.com
V
http://public.kitware.com/Bug/view.php?id=10388 Patch was already included
I would also vote for project_group to get applied.
I'd also like to see support for additional compile flags based on
target http://public.kitware.com/Bug/view.php?id=10389
On Mon, Jul 5, 2010 at 11:31 AM, David
>I'd like to see those fixed:
>http://public.kitware.com/Bug/view.php?id=11030
That one is closed.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-top
On Thu, Jul 29, 2010 at 6:33 PM, Eric Noulard wrote:
> 2010/7/5 David Cole :
>> Now that we have released CMake 2.8.2 last Monday, and we have switched to
>> this new workflow using branches in the git repository, *now* would be a
>> great time to prioritize bug fixes for the next release of CMake
Eric Noulard
writes:
[snip]
> May be I was too pushy on that, sorry.
No problem. Thanks for trying to help.
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep me
On Thursday 29 July 2010, Eric Noulard wrote:
> 2010/7/29 Clifford Yapp :
> > Got it - was using a VTK macro for third_party inclusion that was
> > using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
>
> SUBDIRS is deprecated but it's good to know that it's behavior
> is not stric
2010/7/5 David Cole :
> Hi all,
> Now that we have released CMake 2.8.2 last Monday, and we have switched to
> this new workflow using branches in the git repository, *now* would be a
> great time to prioritize bug fixes for the next release of CMake.
> We are leaning towards quarterly releases fro
Andreas Pakulat writes:
[snip]
> add_custom_command( OUTPUT build.h
> COMMAND cmake -E echo \"\#define FOO \\"bar\\"\" >build.h
> )
Well, it even makes sense, although it is not immediately
obvious. Thanks!
> You can easily see your mistake by running (n)make VERBOSE=1 to
2010/7/29 j s :
> I'm linking C++ static libraries against a c main. On linux, cmake 2.6
> tries to use gcc for the final link. cmake 2.8.1 uses g++ for the final
> link. How do I tell cmake 2.6 to use a c++ linker?
May be setting the LINKER_LANGUAGE
property on the target?
see
http://www.cmake
I'm linking C++ static libraries against a c main. On linux, cmake 2.6
tries to use gcc for the final link. cmake 2.8.1 uses g++ for the final
link. How do I tell cmake 2.6 to use a c++ linker?
Juan
___
Powered by www.kitware.com
Visit other Kitware o
I am a beginner on creating Visual projects with CMake for Cuda applications. I
use the following CMakeLists
cmake_minimum_required(VERSION 2.8)
PROJECT(FermeHedge)
#Searching CUDA
FIND_PACKAGE(CUDA)
#Include the FindCUDA script
INCLUDE(FindCUDA)
SET(SOURCES
aleat_lin.cu
in
Please do not forget to CC the list.
2010/7/29 bal...@t-online.de :
>> Shouldn't you use:
>>
>>TARGET_LINK_LIBRARIES(HelloWorld ${QT_QTGUI_LIBRARY})
>
> Well, if I am _not_ linking statically it works with
> target_link_libraries(HelloWorld QtGui QtCore) without a problem.
> CMake then seems to l
Hi, thanks for the advice, I've now reduced the toolchain file
so the things that make most sense, but I still get the same error.
anyone ?
On Wed, 28 Jul 2010 20:59:45 +0200, Alexander Neundorf
wrote:
> On Tuesday 27 July 2010, j wrote:
>> Hi there,
>>
>> I have a CMakeLists.txt that succesfu
2010/7/29 bal...@t-online.de :
>
> Hello,
>
> I am trying to compile a simple QT HelloWorld.cxx with cmake. I have a
> statically compiled qt installed as well as a non static version.
> What I want is a statically compiled HelloWorld. Cmake allows me to choose my
> static build of QT (using cmak
Hello,
I am trying to compile a simple QT HelloWorld.cxx with cmake. I have a
statically compiled qt installed as well as a non static version.
What I want is a statically compiled HelloWorld. Cmake allows me to choose my
static build of QT (using cmake-gui) by choosing the qmake
binary in the
On 29. Jul, 2010, at 10:18 , Ingolf Steinbach wrote:
> 2010/7/29 Michael Wild :
>> Where is the main() function? In B?
>
> Yes, it would be in B.
>
>> Perhaps it would be a good idea to not compile it into B, but use the file
>> containing main() as the "required file" instead.
>
> This appro
On 29. Jul, 2010, at 10:47 , Hicham Mouline wrote:
> Hello,I have looked at FindQt4.cmake module for 2.8.2, but I can't find the
> code that sets the QT_LIBRARIES variable.Could someone point that out?Regards
It's in UseQt4.cmake.
HTH
Michael
___
P
2010/7/29 Clifford Yapp :
> Got it - was using a VTK macro for third_party inclusion that was
> using SUBDIRS - switching it to ADD_DIRECTORY got me going. Awesome!
SUBDIRS is deprecated but it's good to know that it's behavior
is not strictly equivalent to ADD_DIRECTORY in some case.
--
Erk
M
2010/7/29 Óscar Fuentes :
> Eric Noulard
> writes:
>
>> I think you are wrong.
>>
>> May be you can try the attach script.
>>
>> try:
>> cmake -DYOURSTRING="I like # \ it" -DTHE_FILE=toto.txt -P writeany.cmake
>>
>> You shouldn't have "quite" problem with the previous approach.
>
> I tried this on
Hello,I have looked at FindQt4.cmake module for 2.8.2, but I can't find the
code that sets the QT_LIBRARIES variable.Could someone point that out?Regards,___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com
On 28.07.10 19:19:08, Óscar Fuentes wrote:
> For creating a file at build time with a content like this:
>
> #define foo "bar"
>
> I use this on Linux:
>
> add_custom_command(OUTPUT buildobj.h
> COMMAND ${CMAKE_COMMAND} -E echo "\\#define foo \\\"bar\\\""
> > buildobj.h
> )
>
> but that d
On 29.07.10 09:15:51, Michael Wild wrote:
> On 29. Jul, 2010, at 8:51 , Andreas Pakulat wrote:
> > On 29.07.10 08:37:36, Michael Wild wrote:
> >>
> >> On 29. Jul, 2010, at 6:37 , Óscar Fuentes wrote:
> >>
> >>> Michael Wild writes:
> >>>
> >>> [snip]
> >>>
> Perhaps you need to tell us wh
2010/7/29 Michael Wild :
> Where is the main() function? In B?
Yes, it would be in B.
> Perhaps it would be a good idea to not compile it into B, but use the file
> containing main() as the "required file" instead.
This approach works around the current limitation. But I'd still
consider it sub
On 29. Jul, 2010, at 9:26 , Ingolf Steinbach wrote:
> 2010/7/28 Michael Wild :
>> So, these external libraries should be compiled using ExternalProject_Add
>> (refer to the docs). [...]
>
> Ok. I cannot check right now but your proposed way probably solves that
> problem.
>
>> If I didn't und
On 29. Jul, 2010, at 9:06 , Óscar Fuentes wrote:
> Michael Wild writes:
>
>> The problem is, CMake has to go through the system shell. Of course,
>> CMake could write the command to a file and then invoke a custom
>> interpreter from the system shell, but that would probably be very
>> ineffici
2010/7/28 Michael Wild :
> So, these external libraries should be compiled using ExternalProject_Add
> (refer to the docs). [...]
Ok. I cannot check right now but your proposed way probably solves that problem.
> If I didn't understand your scenario correctly, please provide some more
> detail
On 29. Jul, 2010, at 8:51 , Andreas Pakulat wrote:
> On 29.07.10 08:37:36, Michael Wild wrote:
>>
>> On 29. Jul, 2010, at 6:37 , Óscar Fuentes wrote:
>>
>>> Michael Wild writes:
>>>
>>> [snip]
>>>
Perhaps you need to tell us what it is that you are trying to achieve,
because I susp
Michael Wild writes:
> The problem is, CMake has to go through the system shell. Of course,
> CMake could write the command to a file and then invoke a custom
> interpreter from the system shell, but that would probably be very
> inefficient and would require CMake to implement a full shell
> lan
58 matches
Mail list logo
