I have a development project I've created which uses CMake 2.8.1 to
configure the project to be build on Mac OS X 10.6.4 using Xcode 3.2.1.
The project has several targets in it. Two targets share some source
code files. One of those targets links to some frameworks. The other
target used t
On 26.06.10 13:26:29, Andreas Pakulat wrote:
> On 21.06.10 23:30:46, Andreas Pakulat wrote:
> > On 21.06.10 21:29:14, Alexander Neundorf wrote:
> > > On Sunday 20 June 2010, Andreas Pakulat wrote:
> > > > On 20.06.10 13:27:30, Thiago Macieira wrote:
> > > > > Em Domingo 20. Junho 2010, às 13.07.15,
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.
