| |
| |
Sorry, I was hoping to improve the previous setup, which had its own issues. But I understand how my solution is not perfect either. In the old setup, we would install the `Fluid.app` directory in the `install` path, but not the `fluid` binary. It would instead link into the `Fluid.app` subdirectory structure, IIRC. This did often not work for shell scripts. Omitting `/Applications/Fluid.app` if a custom install path is given is probably the right thing to do here. Not sure if `Fluid.app` should then go into the custom install path somewhere instead.
Albrecht Schlosser schrieb am Dienstag, 16. August 2022 um 13:15:39 UTC+2:
On 8/16/22 10:34 imacarthur wrote:
As a slight aside - is the implication of this that our cmake
script is attempting to install stuff into a "system" location?
I'm not sure how good an idea I think that is... doesn't
sound like a great idea to me, at any rate...
Ian, our CMake script *must* honor the install location given by the
user - or if they don't do it explicitly, then use the CMake default
which is very likely a system location, like '/Applications'
on macOS and IIRC '/usr/local' on Linux.
The issue mentioned in this thread is that the macOS CMake script
ignores the user setting and *always* installs in the system
location due to a change done in the commit mentioned previously in
this thread. This (ignoring user settings) is a bug and I'll try to
fix this, but installing in a system location is not an issue per
se.
It might not be a "good idea" for some reasons (which I know about)
but that's another topic.
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/18839166-1b5f-4dc2-a4bf-b6675c0ad5fan%40googlegroups.com.
[ Direct Link to Message ] | |
|
| |
