On 11/07/2012 04:13 PM, Matthew Brett wrote:
We can warn about it though. Try adding something like this to the end
of CMake's Modules/Platform/Darwin.cmake:
if(IS_DIRECTORY ${CMAKE_OSX_SYSROOT}/Library/Frameworks AND
IS_SYMLINK ${CMAKE_OSX_SYSROOT}/Library/Frameworks/Frameworks)
Hi,
On Thu, Nov 8, 2012 at 6:26 AM, Brad King brad.k...@kitware.com wrote:
On 11/07/2012 04:13 PM, Matthew Brett wrote:
We can warn about it though. Try adding something like this to the end
of CMake's Modules/Platform/Darwin.cmake:
if(IS_DIRECTORY ${CMAKE_OSX_SYSROOT}/Library/Frameworks
On 11/06/2012 03:29 PM, Matthew Brett wrote:
$ ls /Library/Frameworks | grep Qt
Qt3Support.framework
QtCore.framework
Okay.
$ ls -al /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/
total 8
drwxr-xr-x 4 root wheel 136 Jul 13 21:21 .
drwxr-xr-t 3 root wheel 102 Feb 14 2011 ..
Hi,
On Wed, Nov 7, 2012 at 5:33 AM, Brad King brad.k...@kitware.com wrote:
On 11/06/2012 03:29 PM, Matthew Brett wrote:
$ ls /Library/Frameworks | grep Qt
Qt3Support.framework
QtCore.framework
Okay.
$ ls -al /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks/
total 8
drwxr-xr-x 4 root
On 11/07/2012 03:14 PM, Matthew Brett wrote:
http://bugs.python.org/issue14018
Great, that is exactly this issue.
- I guess that explains it... Hum, how frustrating to have to worry
about the bad symlink.
Yes. You'll have to fix them locally. Thanks for reporting back.
-Brad
--
Powered
Hi,
On Wed, Nov 7, 2012 at 12:21 PM, Brad King brad.k...@kitware.com wrote:
On 11/07/2012 03:14 PM, Matthew Brett wrote:
http://bugs.python.org/issue14018
Great, that is exactly this issue.
- I guess that explains it... Hum, how frustrating to have to worry
about the bad symlink.
Yes.
On 11/07/2012 03:41 PM, Matthew Brett wrote:
I was probably thinking of the problem in the same way as you are,
which is: how can I make sure that the build works or fails gracefully
for someone else if they have the same problem?
I'm not interested in spending much time trying to make the
Hi,
On Wed, Nov 7, 2012 at 1:00 PM, Brad King brad.k...@kitware.com wrote:
On 11/07/2012 03:41 PM, Matthew Brett wrote:
I was probably thinking of the problem in the same way as you are,
which is: how can I make sure that the build works or fails gracefully
for someone else if they have the
On 11/05/2012 08:31 PM, Matthew Brett wrote:
Linking CXX executable shiboken
ld: framework not found QtCore
collect2: ld returned 1 exit status
make[2]: *** [generator/shiboken] Error 1
make[1]: *** [generator/CMakeFiles/shiboken.dir/all] Error 2
make: *** [all] Error 2
I get no such
Hi,
On Tue, Nov 6, 2012 at 4:42 AM, Brad King brad.k...@kitware.com wrote:
On 11/05/2012 08:31 PM, Matthew Brett wrote:
Linking CXX executable shiboken
ld: framework not found QtCore
collect2: ld returned 1 exit status
make[2]: *** [generator/shiboken] Error 1
make[1]: ***
On 11/06/2012 01:37 PM, Matthew Brett wrote:
I've attached the diff of the configs.
The diff for generator/CMakeFiles/shiboken.dir/link.txt shows
identical link lines except that 2.8.10 adds
-isysroot /Developer/SDKs/MacOSX10.6.sdk
to honor the CMAKE_OSX_SYSROOT. The change was here:
Hi,
On Tue, Nov 6, 2012 at 11:10 AM, Brad King brad.k...@kitware.com wrote:
On 11/06/2012 01:37 PM, Matthew Brett wrote:
I've attached the diff of the configs.
The diff for generator/CMakeFiles/shiboken.dir/link.txt shows
identical link lines except that 2.8.10 adds
-isysroot
On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
The problem is in commit e7e613e. Patching Darwin.cmake back to revision
43b74793 solves the problem.
The breakage is here:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7e613efbf1da45a2a9e51d11a4022589d79c642
Thanks for tracking it
Hi,
On Mon, Nov 5, 2012 at 7:57 AM, Brad King brad.k...@kitware.com wrote:
On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
The problem is in commit e7e613e. Patching Darwin.cmake back to revision
43b74793 solves the problem.
The breakage is here:
On Nov 5, 2012, at 12:44 PM, Matthew Brett wrote:
Hi,
On Mon, Nov 5, 2012 at 7:57 AM, Brad King brad.k...@kitware.com wrote:
On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
The problem is in commit e7e613e. Patching Darwin.cmake back to revision
43b74793 solves the problem.
The
Hi,
On Mon, Nov 5, 2012 at 12:44 PM, Matthew Brett matthew.br...@gmail.com wrote:
Hi,
On Mon, Nov 5, 2012 at 7:57 AM, Brad King brad.k...@kitware.com wrote:
On 11/04/2012 07:59 PM, Bradley Giesbrecht wrote:
The problem is in commit e7e613e. Patching Darwin.cmake back to revision
43b74793
On 11/5/2012 8:31 PM, Matthew Brett wrote:
Is there something else I can do to find out where the problem is?
make VERBOSE=1 with both and see what the difference is with the link lines.
--
Bill Hoffman
Kitware, Inc.
28 Corporate Drive
Clifton Park, NY 12065
bill.hoff...@kitware.com
Hi,
On Mon, Nov 5, 2012 at 5:47 PM, Bill Hoffman bill.hoff...@kitware.com wrote:
On 11/5/2012 8:31 PM, Matthew Brett wrote:
Is there something else I can do to find out where the problem is?
make VERBOSE=1 with both and see what the difference is with the link lines.
Thanks for the hint.
Seeing the same thing trying to update the MacPorts cmake port to 2.8.10.
The problem is in commit e7e613e. Patching Darwin.cmake back to revision
43b74793 solves the problem.
The breakage is here:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e7e613efbf1da45a2a9e51d11a4022589d79c642
Hi,
Please forgive my ignorance of cmake, but I am running into trouble on
OSX with 2.8.10 and cmake-2.8.10.20121101-gafe0-Darwin64-universal
(but not 2.8.9).
In fact I am trying to compile PySide-1.1.2 :
http://pypi.python.org/pypi/PySide
20 matches
Mail list logo
