Aurélien Gâteau wrote:
> I defined a custom command to generate the .json
Why a custom target? Wouldn't it make sense to generate the json file at
CMake-configure time using execute_process? The desktop file is not
generated.
If that is possible, it 'makes the problem go away'.
However, I th
On Sun, 2013-11-17 at 18:19 -0500, Paul Smith wrote:
> On Mon, 2013-11-18 at 00:18 +0200, Raphael Kubo da Costa wrote:
> > I'm not sure if this is what Roy originally had in mind; it would be
> > good if you could file a bug in CMake's bug tracker for this in any
> > case.
>
> I'm sure this isn't
On Mon, 2013-11-18 at 00:18 +0200, Raphael Kubo da Costa wrote:
> I'm not sure if this is what Roy originally had in mind; it would be
> good if you could file a bug in CMake's bug tracker for this in any
> case.
I'm sure this isn't what Roy was talking about, I just happened to think
of it when I
Paul Smith
writes:
> On Sun, 2013-11-17 at 20:03 +0200, Raphael Kubo da Costa wrote:
>> Roy Crihfield writes:
>>
>> > I have a patch the the CMake emacs mode I'd like to have reviewed and
>> > push. What is the preferred way to do this - should I just send the
>> > patch, or fork and push to th
On Sun, 2013-11-17 at 20:03 +0200, Raphael Kubo da Costa wrote:
> Roy Crihfield writes:
>
> > I have a patch the the CMake emacs mode I'd like to have reviewed and
> > push. What is the preferred way to do this - should I just send the
> > patch, or fork and push to the repository?
>
> Both send
Roy Crihfield writes:
> I have a patch the the CMake emacs mode I'd like to have reviewed and
> push. What is the preferred way to do this - should I just send the
> patch, or fork and push to the repository?
Both sending a patch to cmake-devel via `git patch' and sending a pull
request with Git
