[cmake-developers] Compiling static/stand-alone CMake.exe

[Venedict Tchistopolskii]

Er, lemme clarify.

Can cmake-gui.exe be built along with cmake if using the install path
setting? I currently use windeployqt to handle gui dependencies.

On Thu, Jan 24, 2019 at 9:23 AM Venedict Tchistopolskii <venytch at gmail.com>
wrote:

> I was building it via VStudio and generating the solution via CMake, is
> that wrong?
>
> I need cmake-gui.exe to be built too, would that work with this install
> path setting?
>
> VT
>
> On Thu, Jan 24, 2019 at 9:12 AM Kyle Edwards <kyle.edwards at kitware.com>
> wrote:
>
>> I forgot to mention - building it this way doesn't require the use of a
>> toolchain file - it was in response to this:
>>
>> > *Trying to do so because building CMake without toolchain gives me the
>> below; After I move cmake.exe to another directory:*
>>
>> If you build it as I laid out below, you won't need a toolchain file.
>> Hope this helps!
>>
>> Kyle
>>
>>
>> On Thu, 2019-01-24 at 12:09 -0500, Kyle Edwards wrote:
>>
>> Venedict,
>>
>> To relocate cmake.exe, it's not sufficient to just copy the executable -
>> you have to install all of the modules along with it. You do this by
>> running the "install" target.
>>
>> Given a path to where you want to put CMake, you would build it like this:
>>
>> cmake C:/Path/To/CMake/Source
>> -DCMAKE_INSTALL_PREFIX=C:/Path/To/Where/I/Want/To/Install
>> cmake --build .
>> cmake --build . --target install
>>
>> This will install cmake.exe along with all of its dependencies.
>>
>> Kyle
>>
>> On Thu, 2019-01-24 at 08:42 -0800, Venedict Tchistopolskii wrote:
>>
>> Hey there!
>>
>> *Current toolchain file for compiling CMake using CMake (on WIndows):*
>> SET(CMAKE_SYSTEM_NAME Windows)
>> set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
>> set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
>> set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
>> set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE ONLY)
>> set(CMAKE_TRY_COMPILE_TARGET_TYPE STATIC_LIBRARY)
>>
>> *Unfortunately this konks out with:*
>> CMake Error: The following variables are used in this project, but they
>> are set to NOTFOUND.
>> Please set them or make sure they are set and tested correctly in the
>> CMake files:
>> LIBMD_LIBRARY
>>     linked by target "cmTC_356fd" in directory
>> D:/GitHub/custom_cmake/solutions_cmake/CMakeFiles/CMakeTmp
>>
>> *Trying to do so because building CMake without toolchain gives me the
>> below; After I move cmake.exe to another directory:*
>> CMake Error: Could not find CMAKE_ROOT !!!
>> CMake has most likely not been installed correctly.
>> Modules directory not found in
>>
>> Usage
>>
>>   cmake [options] <path-to-source>
>>   cmake [options] <path-to-existing-build>
>>   cmake [options] -S <path-to-source> -B <path-to-build>
>>
>> Specify a source directory to (re-)generate a build system for it in the
>> current working directory.  Specify an existing build directory to
>> re-generate its build system.
>>
>> Run 'cmake --help' for more information.
>>
>>
>>
>> *Please advise!!*
>>
>> *VT*
>>
>>
>> --
>>
>> Powered by www.kitware.com
>>
>> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>>
>> Kitware offers various services to support the CMake community. For more information on each offering, please visit:
>>
>> CMake Support: http://cmake.org/cmake/help/support.html
>> CMake Consulting: http://cmake.org/cmake/help/consulting.html
>> CMake Training Courses: http://cmake.org/cmake/help/training.html
>>
>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>>
>> Follow this link to subscribe/unsubscribe:https://cmake.org/mailman/listinfo/cmake-developers
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cmake.org/pipermail/cmake-developers/attachments/20190124/535d8277/attachment.html>