Hi,
On Tue, 5 Apr 2016 23:18:41 -0500
Steven Stallion wrote:
> All,
>
> I am currently working on a very large project that contains over 500
> (yes, really) listfiles. A co-worker was looking into some performance
> issues we were seeing during configuration and found something very
> interest
All,
I am currently working on a very large project that contains over 500
(yes, really) listfiles. A co-worker was looking into some performance
issues we were seeing during configuration and found something very
interesting. Currently configuration is taking 1m57s across several
configurations u
On 05.04.2016 23:31, Salazar De Troya, Miguel wrote:
with no line break, whereas the output variable lib_dirs:
message(${lib_dirs})
/usr/lib/lib/usr/lib64/usr/local/tools/vtk-6.1.0/lib/g/g92/miguel/petsc-3.6.2/miguel-opt/lib/usr/local/tools/openmpi-intel-1.8.4/lib/usr/local/tools/ic-14.0.174
I resolved this using the option OUTPUT_STRIP_TRAILING_WHITESPACE in
execute_process().
https://cmake.org/cmake/help/v3.0/command/execute_process.html I had not seen
it.
From: Miguel Salazar mailto:salazardet...@llnl.gov>>
Date: Tuesday, April 5, 2016 at 2:31 PM
To: Miguel Salazar mailto:salaza
Sorry for the spam, but I found out that there is a line break added by CMake
execute_process(COMMAND bash "../grab_libraries.sh" "lib_dirs" "${METHOD}"
OUTPUT_VARIABLE lib_dirs)
grab_libraries.sh is located in the same folder than CMakeLists.txt and I call
cmake .. from a build folder inside
My apologies, the previous error was because of a trailing whitespace. Although
I would still like to know why the terminal variable
/usr/lib;/lib;/usr/lib64;/usr/local/tools/vtk-6.1.0/lib;/g/g92/miguel/petsc-3.6.2/miguel-opt/lib;/usr/local/tools/openmpi-intel-1.8.4/lib;/usr/local/tools/ic-14.0.1
Hello
I am calling find_library in a loop, using the same variable for HINTS. This
variable (lib_dirs) is set using a script, and when I simply print it using
message(), I obtain this output:
message(${lib_dirs})
/usr/lib/lib/usr/lib64/usr/local/tools/vtk-6.1.0/lib/g/g92/miguel/petsc-3.6.2/mi
I ended up using this exact approach with addition of one top level
Makefile which is used to run cmake in build folder. Top level Makefile
takes those arguments and passes them down to the cmake execution, which
than makes a decision on which way to go depending on the argument passed
in.
Here is
Hi Fedja,
As far as I know, the Makefiles generated from CMake cannot contain decisions.
CMake supports several output types aside from Makefiles and some of them
probably don’t support decisions. However, you could supply these arguments
within CMake call using -D option. For example
cmak
Dear All,
I'm stumped on the following, seemingly simple issue.
I need to figure out in my configuration whether a given header file will be
available when I'll try to build my library, or not. So that I could set a
particular definition for the compiler according to whether the file is
availa
10 matches
Mail list logo