That could work too but as the SDK is a single cmake file that rely on
nothing else, I can make a copy of it in my repo, remove the
add_custom_command() call and use that local version until the patch is
done.
It won't force me to change the environment on every computer.
But I'll keep that idea f
In the meantime if this POST_BUILD command calls a specific tool you can create
a no-op shell script with the same name and put its location in the PATH
variable.
Le 6 mars 2019 à 07:41 +0100, Olivier Gomez , a
écrit :
> Thank you for your suggestions.
> I think the best option is a patch but it
Thank you for your suggestions.
I think the best option is a patch but it will take some time ... I guess I
will have to find a workaround in the meantime !
Anyway, thanks again !
Olivier
Le mar. 5 mars 2019 à 18:58, Kyle Edwards a
écrit :
> On Tue, 2019-03-05 at 10:01 -0700, Olivier Gomez wrot
On Tue, 2019-03-05 at 10:01 -0700, Olivier Gomez wrote:
> Hello,
>
> I have been searching for a way to remove a custom command
> (POST_BUILD
> event) from a target in CMake but, so far, I've found nothing.
>
> I tried to add another custom command to override the first one but
> it seems
> to ap
Hello,
I have been searching for a way to remove a custom command (POST_BUILD
event) from a target in CMake but, so far, I've found nothing.
I tried to add another custom command to override the first one but it seems
to append a second command.
I tough that could work because of the first signa
