Le lun. 9 juil. 2018 à 07:14, Anoop C S a écrit :
> Hi all,
>
> While running tests from a wip branch[1] for socket_wrapper project I
> noticed the following output
> on FreeBSD:
>
>
Your issue seems more related with the "socker wrapper" project than with
CMake/CTest but...
> Following that I
Hi all,
While running tests from a wip branch[1] for socket_wrapper project I noticed
the following output
on FreeBSD:
# make test
Running tests...
Test project /root/build
Start 1: test_ioctl
1/25 Test #1: test_ioctl . Passed0.03 sec
Start 2: te
On 2018-07-06 20:34- Clune, Thomas L. (GSFC-6101) wrote:
To use the Intel compiler, one must use an environment variable that specifies
the path to the license file. E.g.,
export INTEL_LICENSE_FILE=/usr/local/intel/license
Other commercial compilers use a very similar mechanism.I
You could user "cmake -E env " in combination with
https://cmake.org/cmake/help/v3.12/prop_gbl/RULE_LAUNCH_COMPILE.html and maybe
https://cmake.org/cmake/help/v3.12/prop_gbl/RULE_LAUNCH_LINK.html if needed.
Am 6. Juli 2018 22:34:04 MESZ schrieb "Clune, Thomas L. (GSFC-6101)"
:
>To use the
Hi,
Could you create a simple compiler wrapper script, and point the
CMAKE_*_COMPILER variables there:
#!/bin/bash
export INTEL_LICENSE_FILE=/usr/local/intel/license
/path/to/ifort "$@"
Regards,
Juan
On 7/8/18 8:41 PM, Clune, Thomas L. (GSFC-6101) wrote:
Unfortunately, I cannot dictate whe
Unfortunately, I cannot dictate where the sysadmins are putting the license
file. I can of course put a copy in /home//Licenses which is another
location that Intel looks by default. And if there is no better solution, I
will provide instructions to all of our developers on making copies
Marc,
Thank you for the suggestion. Unfortunately, I’m a bit confused by the
documentation and not at all sure how to proceed. Further help would be
appreciated.
In particular, I do not see how to capture the existing Fortran, C and CXX
toolchains and then provide the minor extension of set
Hi there,
I'm using a custom script [1] to look for the library sqlite3. However,
the keyword "REQUIRED" (as quietly) is ignored by find_package. That is
even if the library is not found, the script continues is processing:
// CMakeLists.txt
cmake_minimum_required(VERSION 3.10)project(hello_
On 2018 M07 7, Sat 19:09:18 CEST Martin Weber wrote:
> Hi all,
>
> FYI, according to this [1], those generators do no longer work with the new
> core build introduced in CDT 9.5.
>
> Martin
>
> [1] http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg33066.html
do you know whether the new build syst
My parallel builds on my Linux OS (currently Debian Buster, but this
also happened for Debian Jessie so this is a long-standing problem)
have ascii null ('\0) characters inserted in the output while the
corresponding non-parallel build does not have those extra characters.
For example, for the PLp
10 matches
Mail list logo
