On Tuesday 14 February 2012, Brad King wrote:
> On 2/14/2012 1:26 PM, Alexander Neundorf wrote:
> > Well, CMakeConfigHelpers.cmake would be shipped with cmake, so as long as
> > the Config.cmake file says
> > cmake_minimum_required(VERSION 2.8.8)
> > it would be f
On Tuesday 14 February 2012, Yury G. Kudryashov wrote:
> Brad King wrote:
> > On 2/13/2012 4:52 PM, Alexander Neundorf wrote:
> >> we are hoping that more and more libraries will install Config.cmake
> >> files (and for kdelibs this is actually happening right now), so
On Monday 13 February 2012, Brad King wrote:
> On 2/13/2012 4:52 PM, Alexander Neundorf wrote:
> > we are hoping that more and more libraries will install Config.cmake
> > files (and for kdelibs this is actually happening right now), so we
> > should make sure it is straighfor
Hi,
we are hoping that more and more libraries will install Config.cmake files
(and for kdelibs this is actually happening right now), so we should make sure
it is straighforward to create proper Config.cmake files.
IMO the most tricky issue is how to deal with the location of the various
inst
On Monday 30 January 2012, David Cole wrote:
...
> From your original post:
>
> "So when ImageMagick is installed everything behaves as always. But if no
> ImageMagick is installed behaviour was this:
>
> find_package(ImageMagick) -> ImageMagick_FOUND = TRUE"
>
> This is simply clearly inc
On Monday 30 January 2012, Stephen Kelly wrote:
> David Cole wrote:
> > On Sun, Jan 29, 2012 at 11:44 AM, Stephen Kelly
> >
> > wrote:
> >> David Cole wrote:
> >>> OK... nearly complete now. Please review, then reply and tell me if
> >>> you object to any of the 7 commits in this topic branch.
>
On Wednesday 08 February 2012, David Cole wrote:
> The stage is intended only for topics that are imminently going to be
> merged to 'next'...
>
> The following CMake topic branches have been on the stage for quite some
> time without being merged to 'next':
>
> UseEnabledLanguagesForDirectoryInf
On Thursday 02 February 2012, Jim Goodnow II wrote:
> On 2/2/2012 5:35 AM, Brad King wrote:
> > On 2/1/2012 5:51 PM, Jim Goodnow II wrote:
> >> I am working on a CodeLite generator for CMake.
> >
> > Great! I assume you mean http://www.codelite.org/ ?
>
> Yes, the open source IDE.
>
> > > Is th
On Monday 23 January 2012, Brad King wrote:
> On 1/21/2012 5:58 PM, Alexander Neundorf wrote:
> > To get the link line I moved code from
> > cmLocalGenerator::OutputLinkLibraries() into a separate function
> > GetLinkLine(cmTarget, cmComputeLinkInformation).
>
> >
On Wednesday 25 January 2012, Eric Noulard wrote:
> 2012/1/25 Brad King :
> > On 1/24/2012 5:50 PM, Eric Noulard wrote:
> >> cmake --help-module CPackComponent
> >> or any other (untouched module)
> >> cmake --help-module FindQt4
> >>
> >> you'll see that the extra space are there as well.
> >> So
On Friday 20 January 2012, Brad King wrote:
> On 1/19/2012 11:49 AM, Alexander Neundorf wrote:
> > On Thursday 19 January 2012, Brad King wrote:
> >> I think a full solution to this will end up duplicating a lot of the
> >> logic that CMake already has in its C
On Friday 20 January 2012, Brad King wrote:
> On 1/20/2012 8:57 AM, Yury G. Kudryashov wrote:
> > Brad King wrote:
> >> I do not think that explanation is correct. The find_package command
> >> in Config mode will set everything as needed.
> >
> > Yes, so the old explanation is incorrect.
> >
>
On Thursday 19 January 2012, Brad King wrote:
> On 1/18/2012 4:24 PM, Alexander Neundorf wrote:
> > On Wednesday 18 January 2012, Alexander Neundorf wrote:
> >> Hi,
> >>
> >> the variable CMAKE_REQUIRED_LIBRARIES is used by several of the
> >> check-m
On Wednesday 18 January 2012, Alexander Neundorf wrote:
> Hi,
>
> the variable CMAKE_REQUIRED_LIBRARIES is used by several of the
> check-modules for listing additional libraries which should be linked.
> It is common to use variables set by Find-modules for t
Hi,
the variable CMAKE_REQUIRED_LIBRARIES is used by several of the check-modules
for listing additional libraries which should be linked.
It is common to use variables set by Find-modules for this, e.g.
set(CMAKE_REQUIRED_LIBRARIES ${JPEG_LIBRARIES} )
Now, if the module did not simply set JPEG_
On Monday 16 January 2012, Rolf Eike Beer wrote:
> According to documentation you can use the following variable to check if
> your compiler is the GNU one:
>
> CMAKE_COMPILER_IS_GNU
>
> Well, this is actually only true for C++ as in CXX. If your language is C,
> then LANG is not C, but CC. If y
On Wednesday 11 January 2012, Brad King wrote:
...
> > To support the fully flexible version, the developer must calculate the
> > relative path from the configured CONFIG_INSTALL_DIR (where the
> > Config.cmake file goes) to the configured INCLUDE_INSTALL_DIR.
>
> It's not too hard. See ITK for
On Wednesday 11 January 2012, Rolf Eike Beer wrote:
> Am Mittwoch, 11. Januar 2012, 15:32:47 schrieb Brad King:
> > On 1/11/2012 1:31 PM, Rolf Eike Beer wrote:
> > > Am Mittwoch 11 Januar 2012, 13:24:42 schrieben Sie:
> > >> The top-level CMakeLists.txt file in CMake needs to pre-load BZIP2_*
> > >
Hi,
here comes a quite lengthy mail on issues I see in KDE but also in general
with install dirs and CMake.
in KDE we define a set of variables which hold the install destinations for
several different file types:
EXEC_INSTALL_PREFIX(${CMAKE_INSTALL_PREFIX})
SHARE_INSTALL_PREFI
On Sunday 08 January 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Sunday 08 January 2012, Stephen Kelly wrote:
> >> Hi,
> >>
> >> I don't think I've ever seen a direct answer to this question.
> >
> > AFAIK, yes, they
On Sunday 08 January 2012, Stephen Kelly wrote:
> Hi,
>
> I don't think I've ever seen a direct answer to this question.
AFAIK, yes, they should.
FindKDE4Internal.cmake finds Qt, FindPNG.cmake finds zlib.
> Is it something to be decided on a case by case basis? If so, then why is
> there no ge
On Tuesday 03 January 2012, Eric Noulard wrote:
> Sorry sent too soon, finger slipped.
> ...
>
> I have been giving wrong advice about the usage of CMAKE_FIND_ROOT_PATH
> which seems to be "reserved" for cross-compiling whereas
>
> CMAKE_PREFIX_PATH
> CMAKE_INCLUDE_PATH
> CMAKE_PROGRAM_PATH
> CMA
On Tuesday 20 December 2011, David Cole wrote:
> rc2 is tomorrow. And we've already merged in what we're going to accept for
> it.
>
> Unless there's something drastically wrong with rc2, I'm hoping it's
> the last rc before the final 2.8.7.
>
> So this one may have to wait.
I merged it into nex
Hi,
yesterday I pushed the GNUInstallDirs-DebianMultiarch branch to stage.
This has only one commit, it adds support for multiarch on Debian ti
CMAKE_INSTALL_LIBDIR.
I'd like to get that into 2.8.7, but I didn't want to merge it into next
without having it reviewed by you.
So, can you please hav
On Monday 19 December 2011, Clinton Stimpson wrote:
> On Monday, December 19, 2011 01:59:37 pm Alexander Neundorf wrote:
> > On Monday 19 December 2011, David Cole wrote:
> > > Alex,
> > >
> > > Can you take a look at this and see if you know why QtAutomoc is
On Sunday 18 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Sunday 18 December 2011, Alexander Neundorf wrote:
> >> On Friday 16 December 2011, Stephen Kelly wrote:
> >> > Alexander Neundorf wrote:
> >> > > On T
On Monday 19 December 2011, David Cole wrote:
> Alex,
>
> Can you take a look at this and see if you know why QtAutomoc is
> failing on this one dashboard?
>
> http://cdash.org/CDash/testDetails.php?test=126108609&build=1833949
I had a look, the output looks good:
"Automoc for target codeeditor
Hi,
this patch fixes dependency scanning for ASM files:
http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=215d0636544f801c20e9154c642f570df2cfca34
It changes the way the CMAKE_CXX_INCLUDE_PATH and CMAKE_Fortran_INCLUDE_PATH
variables are written into CMakeDirectoryInformation.cmake.
Inste
On Sunday 18 December 2011, Alexander Neundorf wrote:
> On Friday 16 December 2011, Stephen Kelly wrote:
> > Alexander Neundorf wrote:
> > > On Thursday 15 December 2011, Stephen Kelly wrote:
> > >> Alexander Neundorf wrote:
> > >> >> And, again a qu
On Friday 16 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Thursday 15 December 2011, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> >> >> And, again a question regarding wording, currently the warnings
> >> >> gen
On Thursday 15 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> And, again a question regarding wording, currently the warnings
> >> generated by automoc say "Better for a more robust
> >> build." I'd like to have a better
On Sunday 11 December 2011, Alexander Neundorf wrote:
> Hi,
>
> in current CMake HEAD automoc has two modes: strict and not strict.
>
> In strict mode it is behaves exactly how the documentation says:
> "If an #include statement like #include "moc_foo.cpp&quo
On Sunday 11 December 2011, Alexander Neundorf wrote:
> Hi,
>
> I have a small macro/function which I need often during buildsystem
> debugging:
>
> function(PRINT_VARIABLES)
>set(msg "")
>foreach(var ${ARGN})
> if(msg)
> set(msg
Hi,
in current CMake HEAD automoc has two modes: strict and not strict.
In strict mode it is behaves exactly how the documentation says:
"If an #include statement like #include "moc_foo.cpp" is found, the Q_OBJECT
class declaration is expected in the header, and moc is run on the header
file.
I
Hi,
I have a small macro/function which I need often during buildsystem debugging:
function(PRINT_VARIABLES)
set(msg "")
foreach(var ${ARGN})
if(msg)
set(msg "${msg} ; ")
endif()
set(msg "${msg}${var}=\"${${var}}\"")
endforeach()
message(STATUS "${msg}")
end
On Tuesday 06 December 2011, Alexander Neundorf wrote:
> Hi,
>
> On Monday 07 November 2011, Brad King wrote:
> > On 11/6/2011 6:12 AM, Stephen Kelly wrote:
> > > ecm_copy_modules(${CMAKE_BINARY_DIR}/modules FindFoo.cmake
> > >
> > >
On Thursday 08 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > -at the top it contains documentation, so you know which variables to use
> > for that package
>
> This came up on the buildsystem list in August:
>
> http://thread.gmane.org/gmane.comp
On Tuesday 06 December 2011, Brad King wrote:
> On 12/6/2011 1:13 PM, Alexander Neundorf wrote:
> > Does that look like it should cover all use cases, for peopling wanting
> > to selectively use some things from e-c-m, and fearing that something
> > would break if they simply
Hi,
On Monday 07 November 2011, Brad King wrote:
> On 11/6/2011 6:12 AM, Stephen Kelly wrote:
> > ecm_copy_modules(${CMAKE_BINARY_DIR}/modules FindFoo.cmake
> >
> > FindBlub.cmake
> > ECMDoSomething.cmake)
On Sunday 04 December 2011, Stephen Kelly wrote:
> David Cole wrote:
> > I, for one, would really like to see per-target include directories in
> > 2.8.7, even without per-config support to start with. Then, add the
> > per-config support / new generator expressions in a later release.
>
> That se
On Friday 02 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> You said that you can't detect this case, but why do you have to? Isn't
> >> there already a check for the Q_OBJECT macro in the cpp file? Wouldn't
> >> the logic be
On Thursday 01 December 2011, David Cole wrote:
...
> You have two topics on the stage with common parent commits:
> AutomocIncludedDotMocFileHandling (not presently in next) and
> RestoreAutmocKDECompatibility (which is presently in next)...
>
> Are you planning to keep both of these, or are you
On Thursday 01 December 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > Thanks.
> >
> > diff --git a/tier1/solid/solid/audiointerface.cpp
> > b/tier1/solid/solid/audiointerface.cpp
> > index ddf6cbc..98e42b2 100644
> > --- a/tier1/solid/solid/a
On Wednesday 30 November 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Tuesday 22 November 2011, Stephen Kelly wrote:
> >> On 11/22/2011 10:03 PM, Alexander Neundorf wrote:
> >> >> Now when I try to build the frameworks branch using the
On Wednesday 30 November 2011, Brad King wrote:
> On 11/29/2011 2:28 PM, Alexander Neundorf wrote:
> > ...a somewhat related idea: if it will be possible to set include
> > directories per target, and since it is already possible to set compile
> > flags per target, it wou
On Wednesday 30 November 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Tuesday 29 November 2011, Stephen Kelly wrote:
> >> Alexander Neundorf wrote:
> >> >> I can't generate the files. I'm asking people with windows and mac
> >>
On Wednesday 30 November 2011, Stephen Kelly wrote:
> Brad King wrote:
> > On 11/30/2011 9:09 AM, Stephen Kelly wrote:
> >> Brad King wrote:
> >>> Alex was proposing simply to provide the singular name as a variable
> >>> but not
> >>> to cache it. The only reason to cache a variable is when we're
On Tuesday 29 November 2011, Brad King wrote:
> On 11/29/2011 10:53 AM, Stephen Kelly wrote:
> > Qt5Core_LIBRARY is intended to be the thing that users would use in the
> > CMakeLists.txt.
> >
> > I've had another read of the Modules/readme.txt and I guess I need to
> > change it to be consistent.
On Tuesday 29 November 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> I can't generate the files. I'm asking people with windows and mac
> >> setups to generate them and post them for review. I don't have those
> >> setups.
> &
On Tuesday 22 November 2011, Stephen Kelly wrote:
> On 11/22/2011 10:03 PM, Alexander Neundorf wrote:
> >> Now when I try to build the frameworks branch using the cmake next
> >> branch, I get:
> >>
> >> AUTOMOC: error:
> >> /home/stephen/dev/src/kf
...a somewhat related idea: if it will be possible to set include
directories per target, and since it is already possible to set compile flags
per target, it would be nice if I could also set a property on targets which
keeps them from using the global settings at all.
Something like
set_targ
On Friday 25 November 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Friday 25 November 2011, Stephen Kelly wrote:
> >> Stephen Kelly wrote:
> >> > Hi there,
> >> >
> >> > I am working on installing CMake config files from the
On Friday 25 November 2011, Stephen Kelly wrote:
> Stephen Kelly wrote:
> > Hi there,
> >
> > I am working on installing CMake config files from the Qt repository so
> > that there is less need for a FindQt.cmake.
>
> By the way, it would be very helpful if anyone tried to build and test this
> o
On Thursday 24 November 2011, Stephen Kelly wrote:
> Hi there,
>
> I am working on installing CMake config files from the Qt repository so
> that there is less need for a FindQt.cmake.
>
> The motivation is that between releases of Qt and CMake, the features of Qt
> get out of sync with the featu
On Wednesday 23 November 2011, David Cole wrote:
> On Wed, Nov 23, 2011 at 2:09 PM, David Cole wrote:
> > On Wed, Nov 23, 2011 at 2:03 PM, Bill Hoffman
wrote:
> >> On 11/23/2011 12:51 PM, Brad King wrote:
> >>> On 11/23/2011 12:48 PM, Brad King wrote:
> On 11/23/2011 12:43 PM, Brad King wro
On Tuesday 22 November 2011, Stephen Kelly wrote:
> On 11/22/2011 08:43 PM, Alexander Neundorf wrote:
> > On Tuesday 22 November 2011, Stephen Kelly wrote:
> >> On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
> > ...
> >
> >>> Please give the RestoreAu
On Tuesday 22 November 2011, Peter Collingbourne wrote:
> On Tue, Nov 15, 2011 at 06:54:01PM +0100, Nicolas Desprès wrote:
> > On Tue, Nov 15, 2011 at 5:29 PM, Bill Hoffman
wrote:
> > > On 11/11/2011 9:36 PM, Peter Collingbourne wrote:
> > > Note that this generator is *nix only (it relies on POS
On Tuesday 22 November 2011, Stephen Kelly wrote:
> On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
...
> > Please give the RestoreAutmocKDECompatibility branch on cmake stage a
> > try. It should work again, but print a warning if a file includes a
> > moc_foo.cpp, but no
On Tuesday 22 November 2011, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > On Tuesday 22 November 2011, Brad King wrote:
> >> On 11/22/2011 10:03 AM, Stephen Kelly wrote:
> >> > Brad King wrote:
> >> >> We will have to require that the i
On Tuesday 22 November 2011, Alexander Neundorf wrote:
> On Tuesday 22 November 2011, Stephen Kelly wrote:
...
> > This is not uncommon in both KDE and in Qt itself, or any other project
> > where it makes sense to put a QObject-inherited class in the _p.h as an
> > internall
On Tuesday 22 November 2011, Stephen Kelly wrote:
> On 11/22/2011 06:20 PM, Alexander Neundorf wrote:
> > Using Qt5 or Qt4 ?
>
> Qt4.
>
> >> There seems to be several problems:
> >>
> >> * KDE does include "foo.moc" if it wants the header
On Tuesday 22 November 2011, Brad King wrote:
> On 11/22/2011 10:03 AM, Stephen Kelly wrote:
> > Brad King wrote:
> >> We will have to require that the install(EXPORT)
> >> commands be invoked in dependency order (ex. A before B). That way when
> >> the command installing ExportB is writing librar
On Tuesday 22 November 2011, Stephen Kelly wrote:
> On 11/10/2011 10:16 PM, Alexander Neundorf wrote:
> > On Wednesday 02 November 2011, David Faure wrote:
> >> On Monday 31 October 2011 21:47:31 Alexander Neundorf wrote:
> >>> On Monday 31 October 2011, David Faure w
On Thursday 17 November 2011, Alexandru Ciobanu wrote:
> On 2011-11-17, at 3:26 PM, Alexander Neundorf wrote:
> >> [ Regular expressions syntax ]
> >> In terms of regular expressions syntax, the only difference that I've
> >> seen is that TRE treats the cu
On Thursday 17 November 2011, Alexandru Ciobanu wrote:
> Hi everyone,
>
> [ CMake + TRE ]
> I was able to make CMake use TRE, by changing the
> RegularExpression.{cxx,hxx.in} files.
>
> I ran the CMake tests, and 100% pass. See the attached log file.
> (NOTE: Bootstrap, complex, complexOne were i
On Wednesday 16 November 2011, Alexandru Ciobanu wrote:
> Hi Brad,
...
> Advantages of TRE:
> - API very similar to standard regex.h (i.e. easy to integrate with
> CMake) - supports wide characters
> - compiles on many platforms Windows, AIX, HP-UX, you name it.
>
> What do you think about TRE
On Wednesday 16 November 2011, Alexandru Ciobanu wrote:
> Hi,
>
> I was successful in making CMake work with PCRE. As expected, it was
> straightforward.
>
> The problem is that PCRE is also slow. So, I tested the same string and
> regex with multiple different libraries in order to assess perfor
On Tuesday 15 November 2011, Brad King wrote:
> On 11/15/2011 1:24 PM, David Cole wrote:
> > On Tue, Nov 15, 2011 at 1:19 PM, Alexander Neundorf
wrote:
> >> function(check_for_file _file _target)
> >>
> >> if(NOT EXISTS _file)
> >>
> &g
On Monday 14 November 2011, you wrote:
> On 11/14/2011 4:01 PM, Alexander Neundorf wrote:
> >> Instead of adding the code to the bottom of GenerateImportPropertyCode
> >> please create a separate method next to it for that part.
> >
> > D
On Monday 14 November 2011, Brad King wrote:
> On 11/12/2011 3:53 PM, David Cole wrote:
> > And, in my opinion, if there are multiple possible causes of the
> > problem then we should enumerate them in a message to the user,
> > just as you've done here in this email back to me. And we should t
On Saturday 12 November 2011, Patrick Gansterer wrote:
> Hi,
>
> I've created a very simple patch to add the basic support for WindowsCE to
> CMake. I does not provide any automatically architecture detection or so
> on, but enables user to use a vanilla CMake for compiling Windows CE
> projects.
On Saturday 12 November 2011, David Cole wrote:
> On Sat, Nov 12, 2011 at 2:48 PM, Alexander Neundorf
wrote:
...
> "which is vague enough"
>
> My problem with the message is that it is vague.
Possible reasons:
- somebody manually copied/deleted/renamed the files
- a non-d
On Saturday 12 November 2011, David Cole wrote:
> On Sat, Nov 12, 2011 at 12:23 PM, Alexander Neundorf
wrote:
> > On Saturday 12 November 2011, Alexander Neundorf wrote:
> >> Hi,
> >>
> >> I added a branch CheckImportedFileExistenceInConfigDotCMakeFiles cm
On Saturday 12 November 2011, Alexander Neundorf wrote:
> Hi,
>
> I added a branch CheckImportedFileExistenceInConfigDotCMakeFiles cmake
> stage.
This is the commit:
http://cmake.org/gitweb?p=stage/cmake.git;a=commitdiff;h=1b12babe0cef55a0d5531a9d0d453a15598eb467
Alex
--
Hi,
I added a branch CheckImportedFileExistenceInConfigDotCMakeFiles cmake stage.
In this branch, the files created for exported targets by cmake contain extra
checks to verify that the files which are being imported actually exist on
disk.
In theory they always should.
But for whatever reason
On Saturday 12 November 2011, Peter Collingbourne wrote:
> Hi,
...
> --
> Peter
>
> [1] The disproportionately large Ninja run time here seems to be
> caused by a large number of required invocations of the 'automoc'
> command.
I plan to optimize this by only checking those files again w
On Wednesday 02 November 2011, David Faure wrote:
> On Monday 31 October 2011 21:47:31 Alexander Neundorf wrote:
> > On Monday 31 October 2011, David Faure wrote:
> > > This is a typical (kde) case where the .cpp incudes the .moc, for the
> > > object defined in th
On Wednesday 09 November 2011, Peter Collingbourne wrote:
> On Tue, Oct 04, 2011 at 11:21:00PM +0200, Peter Kümmel wrote:
> > On 04.10.2011 23:19, Peter Kümmel wrote:
> > >On 03.10.2011 15:03, Brad King wrote:
> > >>On 10/2/2011 1:41 PM, Peter Collingbourne wrote:
> > >>>I have modified the commit
On Monday 07 November 2011, Alexander Neundorf wrote:
> On Sunday 06 November 2011, Stephen Kelly wrote:
> > Hi,
> >
> > As discussed on the cmake user mailing list, I'm interesting in
> > implementing the feature of target specific and configuration spec
On Sunday 06 November 2011, Stephen Kelly wrote:
> Stephen Kelly wrote:
> > Issues:
> > * I have only tried to implement this with the makefile generator and
> > have so far only tested it with "Unix Makefiles". One of the bugs says
> > XCode can't do source-level includes. Can it do target-level i
On Sunday 06 November 2011, Stephen Kelly wrote:
> Hi,
>
> As discussed on the cmake user mailing list, I'm interesting in
> implementing the feature of target specific and configuration specific
> include
> directories.
>
> http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/39090/fo
On Sunday 06 November 2011, Thiago Macieira wrote:
> On Sunday, 6 de November de 2011 18:42:42 Alexander Neundorf wrote:
> > On Wednesday 02 November 2011, Stephen Kelly wrote:
> > > On 11/02/2011 06:32 PM, David Faure wrote:
> > > >> > #include "f
On Wednesday 02 November 2011, Stephen Kelly wrote:
> On 11/02/2011 06:32 PM, David Faure wrote:
> >> > #include "foo.moc"
> >> > #include "moc_foo.cpp"
> >> >
> >> > This would have generated twice the same moc file, I think. IMO this
> >> > is really confusing.
> >
> > Well there is no rea
Hi,
in ccmake, cmake::GetCMakeCommand() returns a wrong path when ccmake was
invoked from the PATH.
CMakeCommand is in ccmake computed this way (in cmCursesMainForm.cxx):
std::string whereCMake=cmSystemTools::GetProgramPath(this->Args[0].c_str());
whereCMake += "/cmake";
...
this->CMakeInsta
On Wednesday 02 November 2011, Stephen Kelly wrote:
> On 11/02/2011 06:32 PM, David Faure wrote:
> > On Monday 31 October 2011 21:47:31 Alexander Neundorf wrote:
> > No, it's the other way around, in KDE. $ grep Q_OBJECT kautosavefile.*
> > kautosavefile.h: Q_OBJECT $
On Tuesday 01 November 2011, craig.sc...@csiro.au wrote:
...
> If you do that, you create a circular dependency, since CMake requires Qt
> to build its GUI application. Yes, you could build CMake's command line
> tools only, then Qt, then build CMake's GUI app, or alternatively you
> could install
On Tuesday 01 November 2011, Brad King wrote:
> On 11/1/2011 1:20 PM, Alexander Neundorf wrote:
> > Would you prefer XML, JSON or something else ?
>
> I have no preference. If the format is simple enough to parse in CMake
> code then it can't be too hard to parse with a C
On Tuesday 01 November 2011, Brad King wrote:
> On 10/31/2011 5:20 PM, Alexander Neundorf wrote:
> > Not sure what the other cmake developers would think about supporting an
> > additional file format for the Config.cmake files, e.g. xml or json, so
> > they could be easily us
On Tuesday 01 November 2011, Eric Noulard wrote:
> 2011/11/1 Alexander Neundorf :
...
> > and I'd be very happy if this could be solved.
>
> Me too.
> I'll dig a little bit on the Eclipse side again, but generating 2
> files in the source does not look like a big de
On Sunday 23 October 2011, Alexander Neundorf wrote:
> Hi,
>
> I just used ProcessorCount.cmake the first time.
> I noticed a small issue:
> AFAIK module file names in cmake use CamelCase, while the macros/functions
> use underscores: SomeCoolStuff.cmake
Hi,
when using out-of-source builds and the Eclipse CDT project generator, a
"linked resource" is created in the Eclipse project file, which points to
CMAKE_SOURCE_DIR, so the user can browse the source directory.
Now, when CMAKE_BINARY_DIR is a subdirectory of CMAKE_SOURCE_DIR (e.g.
MyProject
On Friday 28 October 2011, Stephen Kelly wrote:
> Hi,
>
> == Summary ==
>
> I'm considering adding some cmake files to Qt, which would be installed by
> Qt, and which would make it easier for CMake based projects to depend on
> Qt.
>
> I'm CC'ing the cmake developers too see what they think of t
On Monday 31 October 2011, David Faure wrote:
> Hi Alex,
>
> The latest changes in cmake-git (probably the merge of
> AutomocFindQ_OBJECTAlwaysInHeader) break the compilation of kde-frameworks.
This is for fixing http://public.kitware.com/Bug/view.php?id=12533
> Before:
>
> Generating kauthacti
On Tuesday 25 October 2011, Stephen Kelly wrote:
...
> I think I read somewhere that next gets re-branched from master
> periodically. How often does that happen?
Usually every Tuesday.
Alex
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/openso
Hi,
I just used ProcessorCount.cmake the first time.
I noticed a small issue:
AFAIK module file names in cmake use CamelCase, while the macros/functions use
underscores: SomeCoolStuff.cmake -> some_cool_stuff()
ProcessorCount.cmake doesn't do this, the function is named processorcount()
IMO we
Hi,
I'm currently trying to add support for the source_group() command to the
Eclipse project generator.
It's not as straighforward as I expected.
I expected that if I do
source_group(Foo FILES main.cpp)
in the CMakeLists.txt, that then in the generate step, there would be a
cmSourceGroup obj
On Friday 07 October 2011, Andrey Ponomarenko wrote:
> Hello,
>
> I have an idea to improve the CMake build system by integrating with the
> abi-compliance-checker [1] tool. It's a tool for checking for API/ABI
> backward compatibility of C/C++ libraries. In the Java world there is an
> alternativ
On Thursday 06 October 2011, Brad King wrote:
> On 10/5/2011 9:47 AM, Stephen Kelly wrote:
> > Thanks for all of your explanations. It seems that introducing a way to
> > do this with one command has some support.
> >
> > So if SOME_FEATURE is true,
> >
> > target_link_libraries(foo bar SOME_KEYW
On Tuesday 04 October 2011, Peter Kümmel wrote:
> On 03.10.2011 15:03, Brad King wrote:
> > On 10/2/2011 1:41 PM, Peter Collingbourne wrote:
> >> I have modified the commit message to include more details, and pushed
> >> a modified branch to github.
> >
> > I've fetched the latest version of the
On Sunday 02 October 2011, Rolf Eike Beer wrote:
> On Sa., 1. Okt. 2011 18:40:09 CEST, Alexander Neundorf
wrote:
> > If library bar internally uses symbols from foo,
> > it needs to link against foo.
>
> Correct.
>
> > But if bar doesn't expose symbols fr
501 - 600 of 831 matches
Mail list logo
