From: Christian S. <sch...@li...> - 2025-06-06 09:53:04
|
On Thursday, June 5, 2025 5:17:13 PM CEST Rui Nuno Capela via Linuxsampler-devel wrote: > On 6/5/25 11:34, Christian Schoenebeck wrote: > > On Tuesday, June 3, 2025 8:53:36 PM CEST TJ Lindgren via > > Linuxsampler-devel wrote: > > > > The problem I have is, I don't see an obvious way how to output where > > cmake is installing to, or how exactly. I tried the only documented way > > which is> > > cmake --install build --verbose > > > > But that does not output anything more than without --verbose. > > > > Rui, you don't have a clue either, right? > > Yes I do, use the following spell: > > # configure: > cmake -DCMAKE_INSTALL_PREFIX=$PREFIX -B build > > # build: > cmake --build build > > # install: much like for make DESTDIR env var might be handy here: \ > cmake --install build The install prefix controls *where* cmake installs to. We already had the prefix set and cmake picks up the requested install prefix correctly (both via CMAKE_INSTALL_PREFIX variable, as well as via --prefix option, doesn't matter). The problem rather is *what* cmake installs. For the QSampler Mac build cmake does not install any file at all: + cmake --install build --prefix /home/persson/mac64/ --verbose -- Install configuration: "Release" For the QSampler Windows build cmake only installs the translation files, but not the most relevant file qsampler.exe: + cmake --install build --verbose -- Install configuration: "Release" -- Up-to-date: /home/persson/win32/share/qsampler/translations/qsampler_cs.qm -- Up-to-date: /home/persson/win32/share/qsampler/translations/qsampler_fr.qm -- Up-to-date: /home/persson/win32/share/qsampler/translations/qsampler_ru.qm Like described in my previous email, cmake --install looks into the file ./build/install_manifest.txt to determine what to install. In case of the Windows build that file only contains those 3 translation files, and in case of the Mac build that file is completely empty. /Christian |