Great, thanks !
On Tue, Sep 24, 2019 at 3:38 PM Brad King wrote:
> On 9/24/19 8:12 AM, Charles Huet wrote:
> > in CMake 3.14 the EXCLUDE_FROM_ALL option of add_subdirectory had a
> behavior change.
> > We are negatively impacted by this change, as we are in the sam
Hi,
in CMake 3.14 the EXCLUDE_FROM_ALL option of add_subdirectory had a
behavior change.
Here is the MR: https://gitlab.kitware.com/cmake/cmake/merge_requests/2816,
implementing the requirement from this ticket:
https://gitlab.kitware.com/cmake/cmake/issues/17149.
We are negatively impacted by
Hi,
I'm having an issue with CUDA (sadly the old-style FindCUDA, not the new
native support of CUDA).
The following CMake file reproduces the issue easily on Windows with any
Visual Studio Generator (14 2015 Win64 being the one I use).
Adding the file generated by cuda_compile_ptx to any target
I personally really like the approach taken by FastBuild where you can
specify a folder in which the source resides, and it will take care of
compiling all the files within.
A checksum to verify if there are new files, and if not no need to
reconfigure.
This could pretty much be used with
Hi,
is this buildsystem by any chance FastBuild ?
Because if so there is an effort (I'd like to say ongoing, but it's been on
hold since the release of 9.7) to implement one here:
https://github.com/packadal/CMake/tree/fastbuild-master
Otherwise I guess it can serve as another example, as far
Hi,
I also worked on a similar prototype, and I think this should be discussed
further and set as a long-term goal for CMake.
The conclusions from the last time this came up were (from the top of my
head):
1)
Lua is the language that should be used, since it is easy to embed on all
the
Hi,
I ported the work of @inbilla to CMake trunk a few months ago, and fixed
quite a few tests on my fork: https://github.com/packadal/CMake
I think it would be best if we tried to synchronize our efforts, since lots
of people are interested in getting a FastBuild generator for CMake !
There is
how I can get this test to pass.
Le lun. 10 oct. 2016 à 19:13, Brad King <brad.k...@kitware.com> a écrit :
> On 10/10/2016 09:39 AM, Charles Huet wrote:
> > * the test CMake.CheckSourceTree does not work with Fastbuild,
> > but I could not get it to work with Ninja
pushed has only a few tests failing, quite a few seem
to be related to a lack of non-source file dependencies as far as I can
tell.
Thanks.
Le jeu. 6 oct. 2016 à 19:33, Charles Huet <charles.h...@gmail.com> a écrit :
> >* Please use Utilities/Scripts/clang-format.bash for
>
ier if I feel like it).
>* Please update the license notices to use the new style that
> we switched to in `master`. Both C++ and .cmake notices
> changed.
Will do.
Le jeu. 6 oct. 2016 à 17:32, Brad King <brad.k...@kitware.com> a écrit :
> On 10/06/2016 08:32 AM, Charles Huet wrote:
- RunCMake.try_compile (Failed)
372 - RunCMake.CrosscompilingEmulator (Failed)
374 - RunCMake.AutoExportDll (Failed)
389 - CMake.ModuleNotices (Failed)
406 - CMake.CheckSourceTree (Failed)
Errors while running CTest
Thanks.
Le ven. 23 sept. 2016 à 17:21, Charles Huet <charle
Sorry I pushed on fastbuild-rebase, as the rebase on master fails evento
self host.
I did not expect this to be merged for 3.7, as I'm not sure I'll have time
to polish it enough for release.
On Fri, Sep 23, 2016, 16:52 Brad King <brad.k...@kitware.com> wrote:
> On 09/23/2016 10:30 AM
be close to what you want, but
there is still some work as I introduced a few regressions in the
refactoring.
Le jeu. 22 sept. 2016 à 21:14, Brad King <brad.k...@kitware.com> a écrit :
> On 09/22/2016 03:02 PM, Charles Huet wrote:
> > is linux/mac support mandatory also ?
>
e platforms.
Best,
Charles
Le jeu. 22 sept. 2016 à 19:26, Brad King <brad.k...@kitware.com> a écrit :
> On 09/22/2016 10:41 AM, Charles Huet wrote:
> > a Fastbuild generator in the works, whose development started on CMake
> 3.2,
> > and was pretty much abandonned for t
Hi,
As some of you may know, there is a Fastbuild generator in the works, whose
development started on CMake 3.2, and was pretty much abandonned for the
past 5 months.
I took the time to rebase it on master, and while there is a lot to clean
up (and some stuff works worse that it used to because
Hi,
I was looking at tools that can do this kind of things myself (however I
was more looking at pre-built binaries redistribution than at a
super-build, since our build time is already quite long).
Does Conan (https://conan.io/) not fit your bill as well ?
Best
Le dim. 14 août 2016 à 02:33,
Hi Rick,
this is something I played with a bit, and while it is completely possible
to make your own little python binding, it will not be merged into CMake,
which means you will have to maintain it on your side.
Also, you will need to write the whole interface yourself, as the current
CMake lib
Yes, sorry about that.
Le mer. 16 mars 2016 à 15:46, Brad King <brad.k...@kitware.com> a écrit :
> On 03/16/2016 04:59 AM, Charles Huet wrote:
> > Sure, done.
> >
> > If you have other ideas on how to improve this patch, I'll be happy to
> > implement them.
&
.
Best
Le jeu. 17 mars 2016 à 15:53, Brad King <brad.k...@kitware.com> a écrit :
> On 03/16/2016 12:13 PM, Charles Huet wrote:
> >> On 03/16/2016 04:59 AM, Charles Huet wrote:
> >>> If you have other ideas on how to improve this patch, I'll be happy to
>
7/2016 11:23 AM, Charles Huet wrote:
> > I added a utility function 'ConvertToNinjaFolderRule' that
> > does the same thing as ConvertToNinjaPath, but makes relative
> > to the source dir, and adds the '/all' suffix.
>
> Great. I've applied the patch with a few style changes
eature and I must say it's
pretty sweet for my use case.
Best
Le mar. 15 mars 2016 à 18:58, Brad King <brad.k...@kitware.com> a écrit :
> On 03/14/2016 05:04 AM, Charles Huet wrote:
> > I modified my patch a bit to use C++98 only, and try to stick
> > to the coding conve
Yeah, makes sense.
Thanks so much for your time
Le lun. 14 mars 2016 à 15:58, Brad King <brad.k...@kitware.com> a écrit :
> On 03/14/2016 05:13 AM, Charles Huet wrote:
> > If the CTest parser parsed the output as XML and not simple text, it
> should be
> > able to rec
> a écrit :
> On 03/10/2016 03:29 AM, Charles Huet wrote:
> > Now the big difficulty in this would be to integrate XSLT2 capabilities
> into CMake.
> [snip]
> > Do you think this coule be viable ?
>
> I'd prefer not to add yet another dependency (on xslt). CTest defines
ke targets.
Please tell me if more modifications are required.
Best.
Le ven. 11 mars 2016 à 16:58, Brad King <brad.k...@kitware.com> a écrit :
> On 03/11/2016 10:48 AM, Charles Huet wrote:
> > Here is a prototype that adds a target for each folder the
> > has th
build targets, but I could
not find the correct way to do it (Install target and such).
I used C++11, but I don't know if this is OK in CMake, I'll refactor if not.
Best
Le jeu. 10 mars 2016 à 15:28, Brad King <brad.k...@kitware.com> a écrit :
> On 03/10/2016 02:58 AM, Charles Huet wrote:
g <brad.k...@kitware.com> a écrit :
> On 03/09/2016 04:13 AM, Charles Huet wrote:
> > We used to use this, by creating a composite image containing the
> reference,
> > generated and diff, but in some cases comparing accurately was tedious.
> > Having the 3 images sep
. 10 févr. 2016 à 19:47, Brad King <brad.k...@kitware.com> a écrit :
> On 02/10/2016 10:57 AM, Charles Huet wrote:
> > When using Unix Makefiles (or MSVC) this causes the subfolder to contain
> > a new Makefile, allowing me to build easily the whole subdir.
> >
> &
human comparison much easier.
Also, we have added some HTML buttons and tables, which we would lose by
using this.
Le mar. 8 mars 2016 à 19:27, Brad King <brad.k...@kitware.com> a écrit :
> On 03/08/2016 11:09 AM, Charles Huet wrote:
> > mostly useful to display images, since so
Hi,
to customize our test results, we developped a small test wrapper that
outputs some HTML markup (mostly useful to display images, since some of
our tests compare images with ImageMagick).
However, this does not work since CMake 3.3 because of the refactoring of
ctest to use cmXMLWriter,
Hi,
I have a folder in my build that is added as such: "add_subdirectory(folder
EXCLUDE_FROM_ALL)"
When using Unix Makefiles (or MSVC) this causes the subfolder to contain a
new Makefile, allowing me to build easily the whole subdir.
I cannot find such a facility with Ninja, which is very
I think this problem already exists.
When "projects build elaborate macro/function systems in the CMake
language", you have to understand the build system program. And in my
experience, those systems are widely different from one another.
I have seen a system where you defined lots of variables,
As long as CMake embeds everything that is required, I don't see the
additional pain (since this is what it already does with the CMake
language).
Le jeu. 14 janv. 2016 à 13:35, Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com> a écrit :
>
> On Wed, Jan 13, 2016 at 10:21 PM, Alexander
Thanks for the insight !
I started going towards python because I am more familiar with it, but Lua
seems to be a better fit for CMake now that I think about the constraints
you listed.
The main point I am getting from your mail is that Kitware may not want to
go down this route, even if
ptionally* moving part of the specification
> to a (stateless) declarative format that IDEs can load/edit/save
> directly.
>
> Specific responses follow.
>
>
>
>
> On 01/11/2016 12:24 PM, Charles Huet wrote:
> > I think these goals aim towards a fas
part of cmake ? And the
> second thing was : why not using the scripting power of an existing
> language like Python(or other one)
> and add CMAKE as a framework / library ?
> Probably a dumb question ! :)
>
> Yann
>
> 2016-01-13 10:34 GMT+01:00 Charles Huet <char
nguage whose implementation we do
>> not fully control unless it is allowed to execute only in isolated and
>> independent snippets. These are not hard goals, but it is a trade-off
>> to keep in mind. Stephen may be able to elaborate more on the snapshot
>> approach
, and it would be pretty easy to add most of
the CMake basic functionalities.
I am not used to writing python, so it might not be idiomatic either, but
hey, it works as a simple proof of concept, and it's all I wanted to do for
now :)
Le lun. 4 janv. 2016 à 08:41, Charles Huet <charles.h...@gmail.
ur POC listfile contains this line:
>
> cmake.init("Ninja", "/media/dev/src/cmaketest",
> "/media/dev/build/cmaketest")
>
> which sets the source and build directories. Is this some temporary
> solution for the POC only?
>
> Tamas
>
not just a dumb
idea, and that others have thought about it.
I'll update with the github as soon as I get it working.
Best
Le lun. 4 janv. 2016 à 01:16, Stephen Kelly <steve...@gmail.com> a écrit :
> Charles Huet wrote:
>
> > * cmCacheManager::AddCacheEntry was ma
Hi,
I'd like to have a discussion about using CMake as a library from python,
and by that I mean not writing CMakeLists.txt files, but python code that
then uses the CMake generators and Find*.cmake in order to leverage both
the power of CMake and Python.
First, a bit of background on the idea
40 matches
Mail list logo
