--
Message: 4
Date: Thu, 15 Jul 2010 22:49:40 -0400
From: Bill Hoffman
Subject: Re: [CMake] Auxiliary fortran link libraries?
To: cmake@cmake.org
Message-ID:<4c3fc8c4.4060...@kitware.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 7/15/2010 5:40
2010/7/18 Alan W. Irwin :
[...]
> # Get the Python version.
> execute_process(
> COMMAND
> ${PYTHON_EXECUTABLE} -c "import sys; print sys.version.split()[0]"
> OUTPUT_VARIABLE PYTHON_version_output
> OUTPUT_STRIP_TRAILING_WHITESPACE
> )
> SET(PYTHON_VERSION ${PYTHON_version_output
On 2010-07-18 12:07-0700 Branan Purvine-Riley wrote:
Unfortunately, I can't think of a way to get out of using hardcoded version
lists, since python is often in specific locations (or has a specific executable
name) based on its version number.
I haven't read through the new "Find Python" work
On Sunday 18 July 2010 09:15:17 Michael Hertling wrote:
> On 07/18/2010 06:50 AM, Branan Riley wrote:
> > I've mad a very cursory effort to add Python 3 support to CMake. All
> > I've done so far is take FindPythonLibs and FindPythonInterp, and
> > change the variable names and the python versions.
On 07/18/2010 06:50 AM, Branan Riley wrote:
> I've mad a very cursory effort to add Python 3 support to CMake. All
> I've done so far is take FindPythonLibs and FindPythonInterp, and
> change the variable names and the python versions. It doesn't yet have
> framework support on Mac, as I have no id
Den 15-07-2010 13:48, Martin Santa María skrev:
I'm trying to create an NSIS installer that contains both release and
I assume this is about NSIS with CPack?
debug targets. I'm using CMake 2.6 and Visual Studio and the installer
always contains the Build version I select in Visual Studio.
Has
