The basics of what I want to do is the following:
Use git to get a list of files that have changed (git status?)
Pipe those files into a custom program that does some code cleanup & formatting.
What I am not sure how to do is entice git to give me a list of files that is
easy for cmake to parse?
Jason Cooper wrote:
> Is there a plan to merge the above into cmake as a module?
>
>> You can of course do something similar for Android:
>>
>> https://github.com/taka-no-me/android-cmake/blob/master/android.toolchain.cmake
>
> Ah, thanks for the heads up. I'll need that later.
There should be
Jason,
I¹ll have to get back to you on that. The problem is the snippets I¹m
referring to are part of a much larger build system I¹ve created for Mac,
Windows, Linux, iOS, Android, Windows Phone, and Native Client, and so you
would likely need a lot of other supporting files to make sense of them.
Parag,
On Thu, Apr 02, 2015 at 02:32:13PM +, Parag Chandra wrote:
> No idea if they have plans to merge any toolchain files directly into
> CMake. Even if they did, cross-compiling is still a process that requires
> explicitly overriding your host computer?s native toolchain, so it?s not
> som
The documentation says:
If UPDATE_DISCONNECTED is set, the update step is not executed
automatically when building the main target. The update step can still
be added as a step target and called manually.
This option sounds interesting but I do not understand how this is supposed
to be used. Wha
No idea if they have plans to merge any toolchain files directly into
CMake. Even if they did, cross-compiling is still a process that requires
explicitly overriding your host computer¹s native toolchain, so it¹s not
something that CMake will sort of do for you automatically - you¹re still
going to
I see now; thank you for the explanation.
Best,
Charles
On Thu, Apr 2, 2015, 7:17 AM Nils Gladitz wrote:
> On 04/02/2015 04:05 PM, Charles Nicholson wrote:
> > Thanks for the quick response, Nils, that fixed it!
> >
> > I'm curious, though, why wasn't simply marking my lib as depending on
> > t
On 04/02/2015 04:05 PM, Charles Nicholson wrote:
Thanks for the quick response, Nils, that fixed it!
I'm curious, though, why wasn't simply marking my lib as depending on
the externalproject_add target enough? I like using the byproducts line
since it's more exact and descriptive, but shouldn't
Thanks for the quick response, Nils, that fixed it!
I'm curious, though, why wasn't simply marking my lib as depending on the
externalproject_add target enough? I like using the byproducts line since
it's more exact and descriptive, but shouldn't it work without that?
Thanks again,
Charles
On We
Parag,
On Wed, Apr 01, 2015 at 05:43:25PM +, Parag Chandra wrote:
> You need to cross-compile in order to target iOS, but if I?m reading your
> command line correctly, you are merely instructing CMake to generate an
> Xcode build system for the host OS, which is naturally going to produce a
>
Hi all,
For one of our projects, I have recently started experimenting with a
build setup based on a single ctest script that performs configure,
build and runs the unit tests. One thing that is slightly bothering me
at the moment with this solution, is that I seem to be unable to set
the build ve
11 matches
Mail list logo