I need to install a library into a directory whose name depends on the machine
type. For example
if (WIN32)
if (CMAKE_CL_64)
set(ARCH_DIR win32)
else()
set(ARCH_DIR win64)
endif()
elseif (UNIX)
if ()
set(ARCH_DIR linux32)
else()
set(ARCH_DIR linux64)
expanded to
the registry value. How is this expansion supposed to happen?
Karl
---
Karl Merkley, Ph.D.
Elemental Technologies, Inc.
Computational Simulation Software, LLC
www.csimsoft.com
Office: 1-801-756-1972, ext 1
On May 3, 2010, at 9:24 AM, Bill Hoffman wrote:
On 5/3/2010 11:11 AM, Tron Thomas wrote:
What is the purpose for the OSX_ARCHITECTURE and
OSX_ARCHITECTURES_CONFIG properties that already exist in CMAKE? It
seems like they might be properties that are already meant to address an
issue like
On May 3, 2010, at 10:11 AM, Sean McBride wrote:
On Mon, 3 May 2010 09:59:36 -0600, Karl Merkley said:
I just read through this entire thread and I would like to expand it a
little. Regardless of platform, what is the right way to determine the
right build architecture? I run on a 32
I was just testing the dmg install on a Mac G5 running Mac OS X
10.4 . I do find it a touch odd that if I choose a directory
($dir) for install that it places it in $dir/usr. This means that
if I want to do an install into /usr/local I get a /usr/local/usr/
bin. That doesn't seem
I'm linking an app with the python library and I have a requirement
to link with the shared library not the static library. It appears
that FindPythonLibs has no way of specifying shared vs. static. The
shared lib actually is installed in /usr/lib. The static lib resides
in
What I found with the module problem was that the parser was picking
up the keyword in the comment. I just did something like add braces
around the module keyword so that the parser was a little more
confused and didn't identify the word module in the comment.
Something like . . .
c
I have a simple Fortran project that I am testing with cmake.
PROJECT(multi_patch Fortran)
SET( SRCS
aAdjKeep.f
Main_mp.f
)
ADD_EXECUTABLE(multi_patch ${SRCS})
However, the first file is a Fortran 95 module and when I try to build I get
the following error.
Scanning dependencies of
Does CPack have any ability to help with the install_name_tool on the
Mac? Mac applications avoid DLL hell by creating an application
bundle that is really a directory structure that includes the
application, the resources, and the shared libraries used by the
application. My
