On 2010-06-26 01:33:54 +0200, Michael Hertling said:
Anyway, one should not take it too lightly; IMO, writing a fully
featured, reliable and consistent FindPython.cmake is rather a
nontrivial task.
True. But it would be great to have sth which performs siginificantly
better than the curren scr
On 25. Jun, 2010, at 22:30 , Janosch Peters wrote:
> On 2010-06-25 18:36:06 +0200, Michael Wild said:
>>> AFAIK all directories you give gcc with the "-I" option will be searched
>>> _before_ the standard include paths or C_INCLUDE_PATH. So I think you do
>>> have control over what is included.
On 06/25/2010 04:11 PM, Janosch Peters wrote:
> On 2010-06-25 15:45:37 +0200, Michael Hertling said:
>
>> On 06/25/2010 03:17 PM, Janosch Peters wrote:
>>> On 2010-06-21 07:01:36 +0200, Michael Hertling said:
>>>
8d87d12
>>>
>>> What's that? Leet speak?
>>
>> No, these are the first seven and
On 2010-06-25 18:36:06 +0200, Michael Wild said:
AFAIK all directories you give gcc with the "-I" option will be
searched _before_ the standard include paths or C_INCLUDE_PATH. So I
think you do have control over what is included. But I know almost
nohting about all the compiling/linking stuff,
On 25. Jun, 2010, at 17:14 , Janosch Peters wrote:
> On 2010-06-25 16:58:47 +0200, Michael Wild said:
>> However, I think it's really difficult to guarantee consistency. If the code
>> to be compiled contains stuff like the following
>> #ifdef __APPLE__
>> #include
>> #else
>> #include
>> #end
On Jun 25, 2010, at 10:05 AM, Janosch Peters wrote:
> On 2010-06-25 16:32:38 +0200, Mark Moll said:
>> On Jun 25, 2010, at 9:11 AM, Janosch Peters wrote:
>>> Ok. But the python dilemma still remains:
>>> 1. FindPythonInterp and FindPythonLibs might still produce inconsistent
>>> results (e.g. li
On 2010-06-25 16:58:47 +0200, Michael Wild said:
However, I think it's really difficult to guarantee consistency. If the
code to be compiled contains stuff like the following
#ifdef __APPLE__
#include
#else
#include
#endif
the compiler will compile against the latest framework installation i
On 2010-06-25 16:32:38 +0200, Mark Moll said:
On Jun 25, 2010, at 9:11 AM, Janosch Peters wrote:
Ok. But the python dilemma still remains:
1. FindPythonInterp and FindPythonLibs might still produce inconsistent
results (e.g. libs and interpreter of different python versions)
2. AFAIK you ca
On 25. Jun, 2010, at 16:32 , Mark Moll wrote:
>
> On Jun 25, 2010, at 9:11 AM, Janosch Peters wrote:
>
>> On 2010-06-25 15:45:37 +0200, Michael Hertling said:
>>
>>> On 06/25/2010 03:17 PM, Janosch Peters wrote:
On 2010-06-21 07:01:36 +0200, Michael Hertling said:
> 8d87d12
What'
On Jun 25, 2010, at 9:11 AM, Janosch Peters wrote:
> On 2010-06-25 15:45:37 +0200, Michael Hertling said:
>
>> On 06/25/2010 03:17 PM, Janosch Peters wrote:
>>> On 2010-06-21 07:01:36 +0200, Michael Hertling said:
8d87d12
>>> What's that? Leet speak?
>> No, these are the first seven and suf
On 2010-06-25 15:45:37 +0200, Michael Hertling said:
On 06/25/2010 03:17 PM, Janosch Peters wrote:
On 2010-06-21 07:01:36 +0200, Michael Hertling said:
8d87d12
What's that? Leet speak?
No, these are the first seven and sufficiently unambiguous digits of
the SHA-1 sum of the commit in CMak
On Fri, Jun 25, 2010 at 9:42 AM, David Cole wrote:
> I would have thought it was a git commit hash... but I cannot find it at:
>
> http://cmake.org/gitweb?p=cmake.git;a=summary
>
>
> Perhaps it's in another git repo?
>
>
Oops. Thanks Michael, for pointing us to
http://cmake.org/gitweb?p=cmake.gi
On 06/25/2010 03:42 PM, David Cole wrote:
> I would have thought it was a git commit hash... but I cannot find it at:
>
> http://cmake.org/gitweb?p=cmake.git;a=summary
>
>
> Perhaps it's in another git repo?
No, it's in your first-order repository:
git clone git://cmake.org/cmake.git
cd cmake
On 06/25/2010 03:17 PM, Janosch Peters wrote:
> On 2010-06-21 07:01:36 +0200, Michael Hertling said:
>
>> 8d87d12
>
> What's that? Leet speak?
No, these are the first seven and sufficiently unambiguous digits of
the SHA-1 sum of the commit in CMake's Git repository that removes
the framework rel
I would have thought it was a git commit hash... but I cannot find it at:
http://cmake.org/gitweb?p=cmake.git;a=summary
Perhaps it's in another git repo?
On Fri, Jun 25, 2010 at 9:17 AM, Janosch Peters wrote:
> On 2010-06-21 07:01:36 +0200, Michael Hertling said:
>
> 8d87d12
>>
>
> What's
On 2010-06-21 07:01:36 +0200, Michael Hertling said:
8d87d12
What's that? Leet speak?
--
Janosch
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages o
On 06/19/2010 12:31 PM, Janosch Peters wrote:
> On 2010-06-18 08:29:25 +0200, Michael Hertling said:
>
>> On 06/17/2010 04:23 PM, Janosch Peters wrote:
>>> I have two python frameworks on my mac: Python2.5 which comes with OS
>>> X, and python2.6 from macports. If I just use
>>> FIND_PACKAGE(Pytho
On 2010-06-18 08:29:25 +0200, Michael Hertling said:
On 06/17/2010 04:23 PM, Janosch Peters wrote:
I have two python frameworks on my mac: Python2.5 which comes with OS
X, and python2.6 from macports. If I just use
FIND_PACKAGE(PythonInterp) and FIND_PACKAGE(PythonLibs) I end up
getting the pyt
On 06/17/2010 04:23 PM, Janosch Peters wrote:
> Hi list,
>
> I try to write a cmake script for a python module. Its finally working
> now, but the solution I came up with is not very nice.
>
> 1. Finding the correct python environment:
>
> I have two python frameworks on my mac: Python2.5 whic
On 2010-06-17 16:23:09 +0200, Janosch Peters said:
3. Copy python files during installation
The python module needs some python files along with the compiled C
module. Currently, I just copy all the stuff using cmakes file()
command. That means, all files are created when the user types in
"cmak
Hi list,
I try to write a cmake script for a python module. Its finally working
now, but the solution I came up with is not very nice.
1. Finding the correct python environment:
I have two python frameworks on my mac: Python2.5 which comes with OS
X, and python2.6 from macports. If I just u
21 matches
Mail list logo
