*Thank you! Sorry for the mess. Builds now :)*

*Just an FYI, I'm using this Preload.cmake file:*
## Required to build GUI
set(CMAKE_PREFIX_PATH "C:\\Qt\\5.12.0\\msvc2017_64" CACHE STRING "" FORCE)
set(BUILD_QtDialog ON CACHE BOOL "" FORCE)

## Standerdizing build options for 64-bit CMake
set(CMAKE_GENERATOR "Visual Studio 15 2017 Win64" CACHE INTERNAL "" FORCE)
set(CMAKE_INSTALL_PREFIX "${CMAKE_CURRENT_LIST_DIR}/standalone" CACHE
STRING "" FORCE)

*Makes it easier to standardize.*

*VT*

On Thu, Jan 24, 2019 at 12:36 PM Kyle Edwards <kyle.edwa...@kitware.com>
wrote:

> On Thu, 2019-01-24 at 12:31 -0800, Venedict Tchistopolskii wrote:
>
> Nevermind, fixed the cmake-gui.
>
>
> Ah OK, then disregard my response.
>
> Would be nice to know how to triger the proper install/release config from
> VStudio, atm I do this:
> cmake . --target install --config Release
>
>
> This looks correct for doing it on the command line.
>
> The VStudio solution should have an "INSTALL" project which does what you
> want.
>
> Kyle
>
>
-- 

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

Reply via email to