|
|
On 2/7/23 13:11 duncan wrote:
... now I have some caching issue which
means that the build process is trying to pull in a
specific version of
the SDK that does not exist on my system any more.
It's happened before when there's been an Xcode update. Not
sure
if it's CLion and its builtin Cmake, or the brew cmake, or
Xcode itself.
But that's an problem on my system, rather than being an
FLTK issue.
It's a CMake issue caused by a macOS (and/or Xcode) update that
replaced the SDK with another version in another folder. CMake uses
the cached value and the build fails.
It happens to me from time to time as well in a bare CMake
environment (not using Xcode, nor CLion). There are two possible
solutions, at least for me, I don't know what you can do in your
CLion build.
(1) The big hammer: just remove the entire build folder and run
CMake again from scratch. This will find the new SDK, and everything
is fine. Hopefully you know how to setup a new build environment
from scratch (i.e. it's not grown over time ...).
(2) I'm using `cmake-gui .`
(note: '.' for current/build
directory) to configure with the CMake GUI, enable the "Advanced"
view, then type in the "Search:" field the offending directory of
the missing SDK (just "SDK" may suffice). For each displayed item,
click on it, then on "X Remove Entry" to remove it. Then you can click on "Configure"
and it will (hopefully) find the new SDK. This works for me.
Don't worry, you can't remove too many entries, they will all be
found again when you click on "Configure".
If you can't use (2) you can edit CMakeCache.txt and remove all
occurrences of the SDK folder and run cmake again.
--
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/5effaf74-6ef0-ede1-9c5f-6066b6530c8e%40online.de.
[ Direct Link to Message ] | |
|
| |