cinder / Cinder

Cinder is a community-developed, free and open source library for professional-quality creative coding in C++.
http://libcinder.org
Other
5.31k stars 939 forks source link

ninja: error: unknown target 'install' #2257

Open Petross404 opened 2 years ago

Petross404 commented 2 years ago

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 commented 2 years ago

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 commented 2 years ago

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 👍