On Jun 4, 2019, at 2:27 PM, Bryan Christ wrote:
> Thanks for the explanation. Yes. The use of the term Library certainly
> added to my confusion. I've been coding on Linux for 20 and the "proper" way
> of doing things on Mac is a bit elusive to me as I stumble around.
Yeah, it must be
On Jun 4, 2019, at 1:33 PM, Bryan Christ wrote:
> I would agree with you, but I've been told that OSX is moving away from it's
> Unix heritage and placing libraries in non-traditional locations (not /usr or
> /usr/local) and that's going to be increasingly the norm in the future.
>
>
On Jun 3, 2019, at 3:27 PM, Juan E. Sanchez wrote:
> It looks like macOS made it so you have to do something like this:
> open
> /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg
>
> for libraries and includes to be put into /usr.
*Libraries* should exist in
On Jun 4, 2019, at 10:56 AM, Bryan Christ wrote:
> Thanks for your suggestions. I went through that thread pretty thoroughly
> trying all of the recommended tips and, unfortunately, nothing seemed to
> work. I also tried running that open command you cited, but there are still
> no includes
On Jun 2, 2016, at 2:56 PM, Alan W. Irwin wrote:
> It appears you want the Fortran equivalent of the CHECK_C_SOURCE_RUNS
> macro. So I suggest you copy that macro (found in
> Modules/CheckCSourceRuns.cmake) to your own source code where your
> other home-grown CMake
On Jan 22, 2016, at 12:24 PM, Guy Harris <g...@alum.mit.edu> wrote:
> CMake has the macros CHECK_C_COMPILER_FLAG and CHECK_CXX_COMPILER_FLAG, which
> allow checking for whether a given C or C++ compiler flag is supported by the
> compiler being used.
>
> However, there's
CMake has the macros CHECK_C_COMPILER_FLAG and CHECK_CXX_COMPILER_FLAG, which
allow checking for whether a given C or C++ compiler flag is supported by the
compiler being used.
However, there's no CHECK_LINKER_FLAG macro, so that you can check whether a
given *linker* flag is supported by the