Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ninja: error: unknown target 'install' #2257

Open
Petross404 opened this issue Oct 22, 2021 · 2 comments
Open

ninja: error: unknown target 'install' #2257

Petross404 opened this issue Oct 22, 2021 · 2 comments

Comments

@Petross404
Copy link

Hi, I am writing an ebuild for cinder to install it with Portage in Linux. Aparrently cmake doesn't generate an install target:

>>> Install media-libs/cinder-9999 into /tmp/portage/media-libs/cinder-9999/image
 * Source directory (CMAKE_USE_DIR): "/tmp/portage/media-libs/cinder-9999/work/cinder-9999"
 * Build directory  (BUILD_DIR):     "/tmp/portage/media-libs/cinder-9999/work/cinder-9999_build"
ninja: error: unknown target 'install'
 * ERROR: media-libs/cinder-9999::testing failed (install phase):
 *   died running ninja install
 * 
 * Call stack:
 *     ebuild.sh, line  127:  Called src_install
 *   environment, line 2650:  Called cmake_src_install
 *   environment, line 1237:  Called die
 * The specific snippet of code:
 *       DESTDIR="${D}" ${CMAKE_MAKEFILE_GENERATOR} install "$@" || die "died running ${CMAKE_MAKEFILE_GENERATOR} install";

Is this going to be supported?

Thanks!

@richardeakin
Copy link
Collaborator

We haven't had a need for an install target, the reason being that usually cinder is submoduled or otherwise maintained locally within the project repo and referenced that way. I suppose it can't hurt anything to add basic install rules, though.

I'm not familiar with 'ebuilds' or Portage so don't have any insights there.

@Petross404
Copy link
Author

We haven't had a need for an install target, the reason being that usually cinder is submoduled or otherwise maintained locally within the project repo and referenced that way. I suppose it can't hurt anything to add basic install rules, though.

I'm not familiar with 'ebuilds' or Portage so don't have any insights there.

It's ok, you don't need to know about portage. Thanks 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants