CMake lacks `install` target
Platform: Aarch64 Linux
Problem description: When trying to compile from source using CMake and Ninja, I see the following error:
30.90 ninja: error: unknown target 'install'
It seems CMake lacks an install target.
Have tried manually installing libs, its symlinks, and headers automatically but to no avail.
Here's an example of how AWS implemented this for their C SDK.
This is likely an extension of #1048.
@morgolock any chance to make this a priority?
Hi @BwL1289
Thanks for raising this, I'll discuss it with the team.
Thank you.
Hi @morgolock. Not trying to be a bother. Please let me know if the team thought this was worth prioritizing. Thank you!
Hi @BwL1289
Yes we will do it, I will ask for this to be in the next release. Once I get confirmation I will let you know.
Thanks @morgolock.
Hi @BwL1289
It's likely we will start working on this in a couple of weeks.
Hope this helps.
@morgolock yes that helps. Thank you.
@morgolock do you have an updated timeline? Thank you.
Hi @BwL1289
We are currently discussing it, once we have a good idea of the effort I will give you an update. I'll know more in the coming days.
Hope this helps
Thanks.
@morgolock following up again. Can you please let me know if the team plans to fix this?
Hi @BwL1289
The following patch will solve the problem. This fix will be present in v24.11
Hope this helps
@morgolock thank you.
@morgolock please reopen this issue. It looks like you guys forgot to merge the patch into 24.11: https://github.com/ARM-software/ComputeLibrary/blob/v24.11/CMakeLists.txt#L335. The patch you mentioned is not present.
FWIW, I forked this repo and implemented the change manually. I can confirm it works. I opened a PR: https://github.com/ARM-software/ComputeLibrary/pull/1151
Hi @BwL1289
Apologies for the confusion, I've reopened the issue.
We cannot merge the PR on github unfortunately, we only publish a snapshot of the main dev repo on github and if we merge a PR it will go out of sync with the release branch in the dev repo.
Apologies for the confusion. This patch will be present in our next release 24.11.1.
Hi @BwL1289
The patch has been included in v24.11.1, please let us know if this solves your problem.
Hope this helps