On Wednesday, November 8, 2017, Shoaib Meenai wrote:
> Running cmake from an x64 developer command prompt and passing -Thost=x64
to cmake should do the trick.
>
Perhaps more advisable is selecting the Visual Studio generator and passing
in the platform at the end: "Visual Studio 15 2017 Win64."
In a CMakeLists.txt I have the following lines of code:
# with this the user will be asked for a path that has then
# lib64 other subdirectories that are specified below
FIND_PATH(CLP_DIR LIBCLP)
SET(CLP_LIB ${CLP_DIR}/LIB64)
# after the user specified CLP_DIR this shows what is expected:
# the
Running cmake from an x64 developer command prompt and passing -Thost=x64 to
cmake should do the trick.
On 11/8/17, 2:26 PM, "CMake on behalf of Paul Smith" wrote:
Hi all. I wonder if someone can help me get CMake to force Visual
Studio to run the 64bit linker instead of the 32bit link
Hi all. I wonder if someone can help me get CMake to force Visual
Studio to run the 64bit linker instead of the 32bit linker. By that I
mean, the link.exe binary built for 64bit, not a linker that produces a
64bit executable.
Sometimes (but not always) when I link my code I get an error from the
Hello,
I have a problem with using CUDA package in cmake.
I've installed CUDA, version 9.0, downloaded from here:
https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&target_distro=Ubuntu&target_version=1604&target_type=runfilelocal
and then to my CMakeList.txt file I a
Hi,
i have some modules which i want to cross-compile for different platforms
which uses different compilers. One of them for example is the arm-gcc
compiler which works over the toolchain file.
Now i have a Renesas RX compiler which uses for example instead of "-I"
for include paths the argu
