Message -
From: "Chuck Atkins" <chuck.atk...@kitware.com>
To: "tim gallagher" <tim.gallag...@gatech.edu>
Cc: "Andreas Naumann" <andreas-naum...@gmx.net>, cmake@cmake.org
Sent: Wednesday, September 9, 2015 11:11:27 AM
Subject: Re: [CMake] CMake + M
The only exception to that (which I am aware of) is if you are on a CRAY system
where the MPI (and BLAS and LAPACK) are baked into the compiler wrappers (cc,
ftn, etc). In those situations, you actually do not want to run
find_package(MPI) or it will throw errors.
Tim
- Original Message
, since what I submitted wouldn't apply against the current version,
it looks like this work supersedes that patch.
Tim
- Original Message -
From: "Brad King" <brad.k...@kitware.com>
To: "tim gallagher" <tim.gallag...@gatech.edu>
Cc: cmake-developers@cmak
used it. So it wasn't an outstanding issue for me -- I just wanted
to help close out an open issue if they were related!
Thanks,
Tim
- Original Message -
From: "Brad King" <brad.k...@kitware.com>
To: "Tim Gallagher" <tim.gallag...@gatech.edu>
Cc: cmake-de
I haven't followed the discussion on this issue, but how does it relate to the
ticket I opened awhile ago?
http://public.kitware.com/Bug/view.php?id=12316
It looks like it may supersede or fix that issue? If so, I guess the issue can
be closed!
Tim
- Original Message -
From: "Brad
the development discussion off-list if you would like and set up a
github for it so we can collaborate and get things moving along.
Tim
- Original Message -
From: Siebren Reker siebren.re...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu
Cc: cmake-developers@cmake.org
Sent
in the stream.
Tim
- Original Message -
From: Siebren Reker siebren.re...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu
Cc: cmake-developers@cmake.org
Sent: Thursday, August 27, 2015 6:32:17 AM
Subject: Re: [cmake-developers] Is there an official FindMKL module?
Hi Tim
it current.
Tim
- Original Message -
From: Siebren Reker siebren.re...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu
Cc: cmake-developers@cmake.org
Sent: Thursday, August 27, 2015 11:16:34 AM
Subject: Re: [cmake-developers] Is there an official FindMKL module?
Hi Tim
We sometime struggled to get it working, but we never had to resort to using a
FindMKL -- FindBLAS and FindLAPACK work just fine for us, provided we do things
correctly.
So long as we have sourced the mklvars script that ships with Intel MKL and we
put:
BLA_VENDOR =Intel10_64lp_seq ccmake
We use a toolchain file to do the same thing:
# the name of the target operating system
SET(CMAKE_SYSTEM_NAME Catamount)
# set the compiler
set(CMAKE_C_COMPILER cc)
set(CMAKE_CXX_COMPILER CC)
set(CMAKE_Fortran_COMPILER ftn)
There is more info on it if you search around:
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
To: cmake cmake@cmake.org
Sent: Friday, March 13, 2015 1:05:42 PM
Subject: Re: [CMake] Prevent ExternalProject from updating git submodules
Hi Nicholas,
I tried that and no luck. I've done both:
ExternalProject_Add
Hi everybody,
I'm plugging away at using the ExternalProject features to package up our code.
Looking at the documentation for ExternalProject_Add, it says:
...
[GIT_SUBMODULES modules...] # Git submodules that shall be updated, all if empty
...
which is cool, but what do I do if I don't want
that doesn't exist, it will crash when it
tries to check out that made up one. But I can't seem to get it to not update
any of them.
Tim
- Original Message -
From: Nicholas Yue yue.nicho...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu
Sent: Friday, March 13, 2015 12:52:41 PM
Hi all,
I'm trying to play with CPack to build an installer for our code and I'm pretty
confused. I am using the self-extracting TGZ generator on CMake 2.8.8. My
CMakeLists.txt is really long, but I included what I think are the important
parts under my signature.
I configure the build and
, I'd
have to use CPack outside of our CMake system?
Thanks,
Tim
- Original Message -
From: Nils Gladitz nilsglad...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu, cmake@cmake.org
Sent: Wednesday, March 11, 2015 6:32:24 PM
Subject: Re: [CMake] Getting empty package with CPack
Sorry about the TABs, I guess emacs defaults to it and I never noticed.
I have attached an updated patch where the tabs are removed and the test for
CMAKE_EXPORT_COMPILE_COMMANDS is also removed.
Tim
- Original Message -
From: Brad King brad.k...@kitware.com
To: tim gallagher
for versions that require it.
Tim
- Original Message -
From: Brad King brad.k...@kitware.com
To: Tim Gallagher tim.gallag...@gatech.edu
Cc: cmake-developers@cmake.org
Sent: Wednesday, November 5, 2014 12:55:04 PM
Subject: Re: [cmake-developers] Assembly/preprocessed targets for Fortran
On 11
Hi all,
I was trying to generate the assembly listing for some Fortran code and while
searching for how to do it in CMake, I came across an email thread from a few
years ago from somebody asking how to do it in C/C++ by running `make
file.s`. I vaguely remembered knowing this at one point so I
am missing something.
I'll also dig into the testing to see what it would take to add the coverage.
Thanks again,
Tim
- Original Message -
From: Brad King brad.k...@kitware.com
To: tim gallagher tim.gallag...@gatech.edu, cmake-developers@cmake.org
Sent: Tuesday, November 4, 2014 3:45:39
to add the coverage.
Thanks again,
Tim
- Original Message -
From: Brad King brad.k...@kitware.com
To: tim gallagher tim.gallag...@gatech.edu, cmake-developers@cmake.org
Sent: Tuesday, November 4, 2014 3:45:39 PM
Subject: Re: [cmake-developers] Assembly/preprocessed targets for Fortran
On 11
on things I
should have done better/differently so I know to do it correctly next time I
have a patch.
Thanks,
Tim
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
To: tim gallagher tim.gallag...@gatech.edu
Cc: cmake-developers@cmake.org, Brad King brad.k...@kitware.com
Have you installed the development package for blas and lapack? Typically
distributions have a library-only package and then a development package that
includes the headers. Check for libblas-dev in Ubuntu.
Tim
- Original Message -
From: Nicholas Kinar n.ki...@usask.ca
To:
?
It's possible it is in something like /usr/include/blas/blas.h and so it isn't
found by default.
Tim
- Original Message -
From: Nicholas Kinar n.ki...@usask.ca
To: tim gallagher tim.gallag...@gatech.edu
Cc: cmake@cmake.org
Sent: Friday, March 1, 2013 12:57:33 PM
Subject: Re: [CMake
Also worth noting:
I just checked on an Ubuntu machine and the header file is called cblas.h, not
blas.h.
If none of that helps, then I'm out of suggestions. I don't use Ubuntu and most
of my code is in Fortran :)
Tim
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
Good read.
The only suggestion I would make is for Unix Makefiles, rather than running
'make -jN' is to run 'make -j -lN' which tells make to use as many cores until
the load is greater than N.
This is nice because if I have a 12 core system, I can do 'make -j -l12' and it
will build using 12
libraries). Makes building things like
Paraview and Python much simpler on those platforms. I called it ModernCray
since I have no idea what else it would be called.
Thanks,
Tim
- Original Message -
From: Eric Noulard eric.noul...@gmail.com
To: tim gallagher tim.gallag...@gatech.edu
Cc: CMake
Hi,
I have a folder inside my code repository we use to store custom modules and
that folder was added to the search path. Inside that folder I added one called
Platform/ and put a custom platform file in there. But CMake says it can't find
the platform file.
Is it possible to add custom
Hi,
I'm working on getting our CMake project to build the other libraries we wrote
and I'm not sure how it needs to be done. Our main code is a git repository and
inside the repo is a lib/ directory with git submodules for our other
libraries.
What is the best way to get the main project to
Interestingly it only does this for C/C++ but does not do it for Fortran source
files (at least in my project when I just tested it) even though -S is a valid
option for Intel and GNU Fortran compilers.
Any possibility that could be corrected?
Tim
- Original Message -
From: Bill
If you want it to find a particular compiler always, you should do:
FC=ifort or gfortran cmake ...
In other words, set the FC environment variable to the desired compiler.
Likewise, FindMPI will find the first mpicc on your path. If that happens to be
the ifort one, that's what you will
, so long as ifort is used
to link things. But sometimes you may want the entire Intel suite to be used,
so you may want to set the CC and CXX variables in your modulefile also.
Tim
- Original Message -
From: Eli Ateljevich e...@water.ca.gov
To: tim gallagher tim.gallag...@gatech.edu
Don't change the compiler.
Do:
find_package(MPI REQUIRED)
add_definitions(${MPI_Fortran_COMPILE_FLAGS})
include_directories(${MPI_Fortran_INCLUDE_DIRS})
link_directories(${MPI_Fortran_LIBRARY_DIRS})
target_link_libraries(parallel code ${MPI_Fortran_LIBRARIES})
if(MPI_EXTRA_LIBRARY)
I reported this awhile back:
http://public.kitware.com/Bug/view.php?id=12316
The patch I attached would work, but it fails in some select cases so it wasn't
put in. I don't remember the details, it may fail when there is no HL or
something. But you can try it and see if it works for your
Put an:
if(CMAKE_BUILD_TYPE STREQUAL Debug)
endif()
guard around the set_property call.
Tim
- Original Message -
From: Robert Dailey rcdailey.li...@gmail.com
To: CMake ML cmake@cmake.org
Sent: Friday, May 4, 2012 4:16:47 PM
Subject: [CMake] Setting COMPILE_FLAGS property on a
You're not using the results of the find_package.
It should look like:
cmake_minimum_required(VERSION 2.8)
project(collision)
enable_language(Fortran)
FIND_PACKAGE(BLAS REQUIRED)
add_definitions(-O3)
add_executable(collision test.f90)
target_link_libraries(collision ${BLAS_LIBRARIES})
Did you try wiping out the existing build and starting it from scratch?
It sounds like there are still some module files floating around from the
previous build with the previous Fortran version.
Tim
- Original Message -
From: Dick Munroe mun...@csworks.com
To: cmake@cmake.org
Sent:
I don't know the specifics of this case, but the only time we've ever had
trouble with F90 modules is when we add a dependency and don't delete the build
tree before trying to reconfigure.
We have several hundred modules, many in the same directory and many used
across directories and don't
In your MKL installation, do you have the mkl_link_tool in the mkl/tools
folder?
Tim
- Original Message -
From: Andreas Voegel andreasvoe...@gmail.com
To: cmake@cmake.org
Sent: Wednesday, February 1, 2012 1:11:02 AM
Subject: [CMake] Intel MKL with FindBLAS and FindLAPACK on OS X?
-
From: Tim Gallagher tim.gallag...@gatech.edu
To: cmake-developers@cmake.org
Sent: Tuesday, January 24, 2012 9:10:43 PM
Subject: [cmake-developers] New module introduction
Hi,
I've been on the users mailing list a few different times to submit patches for
the FindBLAS and FindLAPACK modules and we
Hi,
I've been on the users mailing list a few different times to submit patches for
the FindBLAS and FindLAPACK modules and we found some more bugs with them. It
was known awhile ago that they don't work for the new Intel MKL naming
conventions
Hi,
Is there a module for CheckFortranCompilerFlag? I see one for C and CXX, but
not one for Fortran.
Tim
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
Hi,
I have a CTest script that builds many different tests and sets it to APPEND by
doing:
foreach(TESTCASE ${LESLIE_AVAILABLE_TESTCASES})
set(CTEST_CONFIGURE_COMMAND ./setup.py -t ${TESTCASE}
'{${LESLIE_CONFIGURE_DICT_BASE}}')
ctest_configure(BUILD ${CTEST_REPO_DIRECTORY} APPEND)
Hi,
We have a test case suite setup to run in continuous mode and submit to CDash.
I followed instructions on the wiki
(http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest#Continuous_Builds_.28new_Style.29)
and have a script that's below the signature.
I was under the impression that
the first time, or it's not a continuous
dashboard...
You need logic like that, and do not execute the configure/build/test
steps when nothing came back from the update...
HTH,
David
On Fri, Jan 13, 2012 at 2:11 PM, Tim Gallagher tim.gallag...@gatech.edu wrote:
Hi,
We have a test case suite setup
I like the idea of putting new in #.#.# when features are added, that would
at least be an easy reminder on the documentation page that some things are not
universal to 2.8.*.
I also agree that it's not super clear that back documentation is available on
the wiki. If you look at the
Hi,
I don't know if this will get done, but is it possible for future releases of
CMake to change the name on the website for the documentation? For example, if
you just looked at the URL:
http://www.cmake.org/cmake/help/cmake-2-8-docs.html
and you didn't look at the header (which happens a
Boost takes arguments for versions of the library if you need a concrete
example.
Tim
- Original Message -
From: Alexander Neundorf a.neundorf-w...@gmx.net
To: cmake@cmake.org
Sent: Wednesday, December 14, 2011 5:11:45 PM
Subject: Re: [CMake] Find package with version numbers
On
Message -
From: Tim Gallagher tim.gallag...@gatech.edu
To: cmake@cmake.org
Sent: Monday, December 12, 2011 10:01:54 PM
Subject: [CMake] FindLAPACK problem
Hi,
I sent this out awhile ago, saying it couldn't find the MKL LAPACK. But I think
the problem may be bigger than that because it can't find
building the list of libraries used for lapack, it
does not include threads as it should.
I've submitted another bug report and uploaded patches, again for both master
and release. Ticket number is 12625.
Tim
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
To: cmake
Hi,
I sent this out awhile ago, saying it couldn't find the MKL LAPACK. But I think
the problem may be bigger than that because it can't find non-MKL lapack for me
either. I get:
-- A library with BLAS API found.
-- A library with BLAS API found.
CMake Error at
Hi all,
I don't know if anybody would find this useful or not, but I thought I'd let
everybody know about it and if somebody would like to use it, I can figure out
the best way to get it out there.
We have a fairly extensive python library that we use to setup our code and
manipulate our
I think the CMAKE_SHARED_LIBRARY_PREFIX/CMAKE_SHARED_LIBRARY_SUFFIX variables
would tell you what you want. We use them to determine the output name as:
${CMAKE_SHARED_LIBRARY_PREFX}library target name${CMAKE_SHARED_LIBRARY_SUFFIX}
We also have an if statement in case STATIC libraries are
Using set() as you have done only sets the value in the current scoping unit.
If you did:
set(gtest_force_shared_crt ON CACHE INTERNAL )
then it will be set to ON and hidden from the GUI display.
If it will always be a bool and you want it displayed on the GUI, you can also
do:
made a mistake in his
reply.
I don't know personally, I've never used this.
Steven
On Wed, Nov 2, 2011 at 9:36 PM, Dan Kegel d...@kegel.com wrote:
On Wed, Nov 2, 2011 at 6:21 PM, Tim Gallagher tim.gallag...@gatech.edu
wrote:
Using set() as you have done only sets the value in the current
: cmake@cmake.org
Sent: Monday, October 17, 2011 3:06:48 AM
Subject: Re: [CMake] CTest outside of CMake
2011/10/17 Tim Gallagher tim.gallag...@gatech.edu:
Hi,
We have our project set up to run a series of test cases, but we are treating
it as if we are not using CMake. I found a tutorial online
...@mail.gatech.edu
Cc: cmake@cmake.org
Sent: Monday, October 17, 2011 11:54:57 AM
Subject: Re: [CMake] CTest outside of CMake
On Mon, Oct 17, 2011 at 11:04 AM, Tim Gallagher
tim.gallag...@gatech.edu wrote:
Hi,
Sorry I wasn't clearer. That section was from a script that we call with
ctest
I'm still trying to figure this one out. I went in an unset _libdir and
manually set it to include the mkl path (even though it is the first thing on
the LD_LIBRARY_PATH) and it still can't find it. In other words,
set(_libdir /usr/local/lib /usr/lib /usr/local/lib64 /usr/lib64
Hi,
We're having problems with FindLAPACK in the latest source head. It claims it
cannot find LAPACK when previous versions of CMake find it just fine. It does
not work with either the Generic version or the Intel version. FindBLAS
correctly locates the library though.
And when we put in the
Hi,
We have our project set up to run a series of test cases, but we are treating
it as if we are not using CMake. I found a tutorial online on how to set it up,
and we have it running just fine when we want to run all of the tests. But, I
haven't figured out how to do the configure/build
Hi,
Is it possible to make CTest aware of other CTest things going on? For example,
let's say I have a continuous build set up for two different projects, and each
has 1 test in it that uses all the processors in the machine.
Is it possible to set it up in a such a way that the two different
Hi,
I was looking around on the internet for how to attach files, specifically
images, to CDash submissions with CTest. I saw some other mailing list posts
related to it in which people said the attached files were showing up as plain
text instead of images on the dashboard.
The solution was
Sent: Monday, September 19, 2011 2:29:47 AM
Subject: Re: [CMake] export() vs. install(export...)
On 09/19/2011 01:14 AM, Tim Gallagher wrote:
Hi,
I've been trying to figure out the exact differences between the
export() and install(export ...) functions and I have some questions
still
Hi,
I've been trying to figure out the exact differences between the export() and
install(export ...) functions and I have some questions still.
From the documentation, EXPORT() makes available the build tree for a given
target and puts the path to the build tree in the
Hi,
I asked about this awhile back and haven't had any luck with it, so I'll try
again.
What we are trying to do is have a project (called Utilities) that has a bunch
of targets (the actual utility executables). Let's say there are 4 utils: pre,
post, grid, and restart. We would like to do
Hertling mhertl...@online.de
To: cmake@cmake.org
Sent: Sunday, August 28, 2011 8:33:47 PM
Subject: Re: [CMake] Install optional targets
On 08/29/2011 01:20 AM, Tim Gallagher wrote:
Hi,
I asked about this awhile back and haven't had any luck with it, so I'll try
again.
What we are trying to do
09 Aug 2011 04:28:51 PM CEST, Tim Gallagher wrote:
In your leaf CMakeLists.txt, try doing:
set_source_files_properties(${SOURCE_FILES} PROPERTIES COMPILE_FLAGS
${LOCAL_COMPILE_FLAGS})
where ${SOURCE_FILES} is a list of the files in the directory and
${LOCAL_COMPILE_FLAGS} is the list
Hi,
How do we tell the project to use the compilers found by FindMPI? On the master
branch, FindMPI has been modified to create MPI_LANG_COMPILER, etc.., but how
does one then specify that it should be used rather than the
CMAKE_LANG_COMPILER?
Tim
${CMAKE_Fortran_COMPILER_ID})
Which works, but I can't find where the compile flags are coming from. It's not
using CMAKE_Fortran_FLAGS_*, but it does change it's flags based on the build
type. Anybody have any idea how to set the flags?
Tim
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
Hi,
We have a project that has a main executable and dozens of utility executables
that may or may not be needed. We can add an executable for each util with
EXCLUDE_FROM_ALL defined so just typing make only does the main code and
something like 'make grid' compiles the grid generator.
But,
Hi,
I'm trying to set up automated testing of our code with CTest (we are using
CMake), but I'm running into some issues I can't figure out the correct way to
solve. Many of our tests require specific sets of options to be turned on/off
in the configuration step.
How is this done? We've used
and if our guys are
just lazy/crazy :)
Tim
- Original Message -
From: Michael Wild them...@gmail.com
To: cmake@cmake.org
Sent: Monday, June 13, 2011 6:09:07 AM
Subject: Re: [CMake] ccmake options organization
On 06/13/2011 11:01 AM, Alexander Neundorf wrote:
On Friday 10 June 2011, Tim
Hi all,
We have a code that has a lot of options to enable/disable at compile time, and
we'd also like to use ccmake to generate input files to run the code (possibly
several hundred options combined). But the way the curses gui organizes things
makes it really hard/tedious to keep track of
the lines giving the .a files.
I will try to think of a general way to make this work, but I'm not very well
versed in cmake. So if anybody has any suggestions or knows how to fix it, we'd
sure appreciate it!
Tim
- Original Message -
From: Tim Gallagher tim.gallag...@gatech.edu
To: cmake
Will,
Sorry for the delay in responding. We tested the FindHDF5 you attached and it
correctly located the Fortran libraries.
Thanks for including it in the updated version!
Tim
- Original Message -
From: Will Dicharry wdicha...@stellarscience.com
To: J.S. van Bethlehem
There's two ways we do it. If you are starting with a clean cache (first time
you run ccmake), if you do:
CC=icc FC=ifort ccmake /path/to/source
It will set it up using Intel compilers.
We also do:
include(CMakeForceCompiler)
CMAKE_FORCE_C_COMPILER(icc Intel C Compiler)
We do this:
if(NOT CMAKE_Fortran_FLAGS_RELEASE)
set(CMAKE_Fortran_FLAGS_RELEASE -O2 -xhost CACHE STRING FORCE)
endif()
In other words, if the flags haven't been set yet (initial start up), set them
to what we want. If they have been set (either changed by the user, or
specified on the
and default value for CMAKE_Fortran_FLAGS_RELEASE is
empty, isn't it?
So the tricky point is to place customization code in proper place.
In my case
==
set(CMAKE_CXX_FLAGS_DEBUG -g -wall
CACHE
STRING
)
==
works perfectly if put at the top of CMakeLists.txt
28.04.2011, 19:23, Tim Gallagher
Hi,
Is there a way (and if not, how do I submit a feature request) to have a set of
drop-down type options in the ccmake interface? The obvious example is for
CMAKE_BUILD_TYPE, where something like hitting Enter scrolls through Release -
Debug - MinSizeRel, etc..
Maybe somebody has already
Hi,
We ran into an issue using CMake with our fortran project. We have
constructions such as:
...
#ifdef OPTION1
USE Module1
#else
USE Module2
#endif
...
It's not actually finding modules as dependencies. Any thoughts? I am using
version 2.8.1, I can try to upgrade if somebody thinks it
...@mail.gatech.edu
Cc: Tim Gallagher tim.gallag...@gatech.edu, cmake@cmake.org
Sent: Tuesday, March 29, 2011 5:13:56 PM
Subject: Re: [CMake] Fortran dependency scanning
On 03/29/2011 11:53 AM, Tim Gallagher wrote:
Hi,
We ran into an issue using CMake with our fortran project. We have
constructions
Hi,
Our project uses HDF5 and Fortran, and while I was looking through the comments
in the FindHDF5.cmake file, I saw that it doesn't support finding the Fortran
bindings. So, I modified it to make it work to find the Fortran bindings.
Below is the diff output. Let me know if there's a more
: Brad King brad.k...@kitware.com
To: Tim Gallagher tim.gallag...@gatech.edu
Cc: gtg0...@mail.gatech.edu, cmake@cmake.org
Sent: Tuesday, March 8, 2011 8:28:08 AM
Subject: Re: [CMake] Cmake with Cray Fortran
On 03/07/2011 09:54 PM, Tim Gallagher wrote:
How can I get it to drop the -rdynamic option
=5abfb571843dba949e010f3b2840d8882d0f3d73
On Sat, Mar 5, 2011 at 11:21 AM, Eric Noulard eric.noul...@gmail.com wrote:
2011/3/5 Tim Gallagher tim.gallag...@gatech.edu :
Eric,
Excellent! Thanks!
I don't know a whole lot about CMake (yet) -- would it be possible to make
older versions aware
machines.
Thanks agian,
Tim
- Original Message -
From: Eric Noulard eric.noul...@gmail.com
To: gtg0...@mail.gatech.edu
Cc: Tim Gallagher tim.gallag...@gatech.edu, cmake@cmake.org
Sent: Saturday, March 5, 2011 3:23:53 AM
Subject: Re: [CMake] Cmake with Cray Fortran
2011/3/5 Tim Gallagher
: Eric Noulard eric.noul...@gmail.com
To: gtg0...@mail.gatech.edu
Cc: Tim Gallagher tim.gallag...@gatech.edu, cmake@cmake.org
Sent: Saturday, March 5, 2011 11:21:20 AM
Subject: Re: [CMake] Cmake with Cray Fortran
2011/3/5 Tim Gallagher tim.gallag...@gatech.edu:
Eric,
Excellent! Thanks!
I don't
Hi,
I have a question about CTest that maybe somebody can point me in the right
direction. Let's say I have two unit tests, one tests a function F1 and the
other tests a function F2 where F2 calls F1.
Is it possible to tell CTest not to run the test on F2 if the test on F1
failed? I saw
Hi,
I'm trying to use cmake with the Cray Fortran compiler. The compiler is wrapped
through a script called ftn.
When I have the PrgEnv-pgi (pgi compiler) or the PrgEnv-gnu modules loaded, it
works with no issue.
But, when I have it set to PrgEnv-cray, it doesn't work.
I manually compiled
Hi,
I'm trying to use cmake with the Cray Fortran compiler. The compiler is wrapped
through a script called ftn.
When I have the PrgEnv-pgi (pgi compiler) or the PrgEnv-gnu modules loaded, it
works with no issue.
But, when I have it set to PrgEnv-cray, it doesn't work.
I manually compiled
88 matches
Mail list logo
