|
From: Chris C. <chr...@gm...> - 2020-01-08 01:41:12
|
Whoops, sorry everybody, it was user error: I had accidentally downloaded the 32 bit version of 3rdParty while trying to make a 64 bit build. Fixed that and now I'm moving again. On Tue, Jan 7, 2020 at 5:15 PM Geoff McLane <ub...@ge...> wrote: > Hi Chris, > > Wow, it just points to the standard cmake handler, when some find package > fails... it takes time to learn cmake... and the output... > > In the current config, cmake can NOT find ZLIB... that is what you need to > address... > > Try setting ZLIBDIR in the environment... and/or the cmake command line, > -DZLIB_ROOT=x:\3rdParty.x64 ... > > The variable ZLIB_INCLUDE_DIR is NOT a user cmake option... but after the > cmake config, in CMakeCache.txt, it should show as > X:\3rdParty.x64\include... > > So far this is just a `config` problem, but if not resolved, then please > ask... here, or OL... > > HTH, Geoff. > On 08/01/2020 01:49, Chris Calef wrote: > > Well damn, this is proving to be a sticky one. Would anyone who has built > on Windows using one of these methods mind telling me the value of their > "ZLIB_INCLUDE_DIR" variable in CMake? I have tried pointing it at the > 3rdParty/include folder, where zlib.h exists, and at the base directory of > a new zlib source download where all the zlib headers exist, and so far all > I get is: > > CMake Error at F:/Program > Files/CMake/share/cmake-3.12/Modules/FindPackageHandleStandardArgs.cmake:137 > (message): Could NOT find ZLIB (missing: ZLIB_INCLUDE_DIR) (Required is at > least version "1.2.4") > > I'm having a hard time debugging this problem at all since the only error > messages point back to my CMake install in Program Files, not to any of the > CMakeLists files in the FG directories. > > > _______________________________________________ > Flightgear-devel mailing list > Fli...@li... > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > |