It appears to work.
Dick Munroe
On 9/10/13 1:49 PM, Brad King wrote:
On 09/10/2013 11:37 AM, Dick Munroe wrote:
However, given that the version of Intel Fortran that actually uses 9.10
as a project format is very, very old I would strongly suggest
defaulting the intelVersion string to:
intelV
On Tuesday, September 10, 2013 09:43:59 AM Dan Kegel wrote:
> Howdy!
> I'm using 2.8.9 installed on MacOSX using macports, and am trying to get
> a minimal example of rpath working.
>
> Doing it without cmake works fine; see
> http://kegel.com/macosx/rpath/demo.txt
> which just does
> gcc -sha
On 2013-09-10 17:38, Littlefield, Tyler wrote:
First, I can create a demo directory and from there I can have a
cmakelists.txt per demo. Is there a way somehow to link to the generated
static library?
Sounds like you are looking for 'target_link_libraries'?
If I move the CXXFLAGS_DEBUG/etc to
On Tue, Sep 10, 2013 at 10:43 AM, Clinton Stimpson wrote:
> Using the INSTALL_RPATH property doesn't work correctly unless you use CMake
> 2.8.12 with the target property MACOSX_RPATH=1.
Done, example http://kegel.com/macosx/rpath/demo2/CMakeLists.txt
> If you want it to work with the older vers
On Tuesday, September 10, 2013 04:03:08 PM Dan Kegel wrote:
> On Tue, Sep 10, 2013 at 10:43 AM, Clinton Stimpson
wrote:
> > Using the INSTALL_RPATH property doesn't work correctly unless you use
> > CMake 2.8.12 with the target property MACOSX_RPATH=1.
>
> Done, example http://kegel.com/macosx/r
On 9/10/2013 6:43 PM, Matthew Woehlke wrote:
On 2013-09-10 17:38, Littlefield, Tyler wrote:
First, I can create a demo directory and from there I can have a
cmakelists.txt per demo. Is there a way somehow to link to the generated
static library?
Sounds like you are looking for 'target_link_lib
That's the problem. Will switch and rebuild.
Dick
On 9/10/13 5:37 PM, Brad King wrote:
On 9/10/2013 5:10 PM, Brad King wrote:
On 09/10/2013 04:56 PM, Dick Munroe wrote:
VS 2010 complains about a the project being created by a later version
of the compiler which would indicate that the intelV
Yeah, I figured that out eventually. It would be a bit more obvious if
that option was named something like:
BUILD_CMake_GUI
or something that obviously connected with what I wanted to do, e.g.,
build cmake-gui.
Best,
Dick Munroe
On 9/9/13 10:17 AM, Robert Maynard wrote:
You need to enab
Hello:
Thanks for the info. Here's what I have so far. In my top-level dir:
#xlog CMake file
cmake_minimum_required (VERSION 2.6)
project(xlog)
Set(xlog_VERSION_MAJOR 1)
Set(xlog_VERSION_MINOR 0)
add_subdirectory(lib)
in lib:
#lib configuration
set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -march=
On 9/10/2013 5:10 PM, Brad King wrote:
> On 09/10/2013 04:56 PM, Dick Munroe wrote:
>> VS 2010 complains about a the project being created by a later version
>> of the compiler which would indicate that the intelVersion is wrong when
>> the project is generated.
>
> What version do you actually
VS 2010 complains about a the project being created by a later version
of the compiler which would indicate that the intelVersion is wrong when
the project is generated.
Dick
On 9/10/13 1:49 PM, Brad King wrote:
On 09/10/2013 11:37 AM, Dick Munroe wrote:
However, given that the version of In
Well I built cmake from the git repository. It gets to the process of
finding a working Fortran compiler and hangs.
Dick
On 9/10/13 1:49 PM, Brad King wrote:
On 09/10/2013 11:37 AM, Dick Munroe wrote:
However, given that the version of Intel Fortran that actually uses 9.10
as a project forma
On 09/10/2013 04:56 PM, Dick Munroe wrote:
> VS 2010 complains about a the project being created by a later version
> of the compiler which would indicate that the intelVersion is wrong when
> the project is generated.
What version do you actually see in the .vfproj files?
-Brad
--
Powered by
Having said that, if cmake knows that the executable is static, it shouldn't
try to change the RPATH.
Is the RPATH in the uninstalled executable empty ?
Yes, the RPATH in the static build is empty. There's isn't a dynamic
section at all, so there is no RPATH in the file.
That said, this issu
On Tuesday 10 September 2013, Jim Leek wrote:
> I'm building a project on Linux x86_64 with 2.8.10.1. I set up the
> project to build statically and shared. However, when I run make
> install on a statically built version I get:
>
> CMake Error at cmake_install.cmake:45 (FILE):
>file RPATH_C
The CMake 2.8.12 release candidate stream continues!
This is the last RC unless a critical, must-fix issue is found.
You can find the source and binaries here:
http://www.cmake.org/files/v2.8/?C=M;O=D
Some of the notable changes in this release are:
- Introduced target_compile_options command
-
I'm building a project on Linux x86_64 with 2.8.10.1. I set up the
project to build statically and shared. However, when I run make
install on a statically built version I get:
CMake Error at cmake_install.cmake:45 (FILE):
file RPATH_CHANGE could not write new RPATH:
/usr/gapps/psuade/
All is well. I updated my minimal examples showing how to do it in
various worlds.
http://kegel.com/macosx/rpath/demo1/ - commandline gcc example
http://kegel.com/macosx/rpath/demo2/ - cmake 2.8.12 example
http://kegel.com/macosx/rpath/demo3/ - cmake 2.8.9 example
Someday I'll add a cross-pla
On 09/10/2013 11:37 AM, Dick Munroe wrote:
> However, given that the version of Intel Fortran that actually uses 9.10
> as a project format is very, very old I would strongly suggest
> defaulting the intelVersion string to:
>
> intelVersion - "11.0" ;
Thanks. I constructed a change based on th
On 9/10/2013 1:42 PM, Stewart, Robert wrote:
Likewise, I want an NSIS installer or RPM that will create
that directory structure in either a default location from my
CMakeLists.txt or in a directory selected by the user during
installation (via the GUI for NSIS or --prefix for rpm).
What must I
I had thought, from reading
http://www.kitware.com/blog/home/post/510
and the doc, that the only thing being added in 2.8.12 was
the MACOSX_RPATH variable.
I guess this is a documentation failure, and/or an example
of cmake's tendancy to accept and ignore garbage input.
cmake, bless its useful li
Anyone?
Stewart, Robert wrote, on Thursday, September 05, 2013 12:55 PM:
>
> I want CPack to build packages that result in installing
> files in a particular structure, regardless of whether I'm
> using TGZ, ZIP, NSIS, RPM, etc. I'm having trouble making
> this work and need help.
>
> Let me make
The clue is probably that RPATH support on the Mac is "behind" and has
only recently been merged to master... -- although you didn't say
exactly how much you'd be willing to pay for a clue... :-)
Here are some related commits:
http://cmake.org/gitweb?p=cmake.git&a=search&h=refs%2Fheads%2F
Howdy!
I'm using 2.8.9 installed on MacOSX using macports, and am trying to get
a minimal example of rpath working.
Doing it without cmake works fine; see
http://kegel.com/macosx/rpath/demo.txt
which just does
gcc -shared foo.c -install_name @rpath/foo.so -o foo.so
gcc -Wl,-rpath $OTHERDIR x
No patch, but the fix is in cmLocalVisualStudio7Generator.cxx
Search for: intelVersion
Shortly afterward there is an if statement that begins if
(intelVersion.find("13")...
Add:
intelVersion.find("14) == 0 ||
to the if statement.
However, given that the version of Intel Fortran that actual
25 matches
Mail list logo
