Reopened the bug because this is _still_ an issue with CMake 2.8.3. Just tried
to configure, build and install and got the same crash.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer
On 1/5/2011 10:05 AM, Michael Jackson wrote:
Reopened the bug because this is _still_ an issue with CMake 2.8.3.
Just tried to configure, build and install and got the same crash.
Can you try it with the current master branch?
___
Mike
Try the download from the CMake website, source download that is. Then
configure and build and then install it.
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
Sure. And _that_ does work. Just curious how that bug fell through versions
2.8.0, 2.8.1, 2.8.2, 2.8.3? I guess there isn't a test for actually verifying
that the built Qt app actually launches during the test or the CMake GUI is
always guilt with carbon during the testing which would alleviate
This should have been fixed with the switch to using BundleUtilities
for CMake's bundle.
The 2.8.3 BundleUtilities should copy in the Resources necessary for
this to work.
So I think that was done (switch to using built in BU) just *after* 2.8.3.
Unless there's still a missing qt.conf file
Note that I am using the ./configure to configure CMake itself. Not CMake to
configure CMake. So maybe there is something missing from those installs. The
interesting part (with all the discussions with putting in bug reports) is that
I even provided a patch for 2.8.0. Something got put into
cmake-gui needs some further work to be automatically testable.
If we launched it as-is on a test run, then it would just hang there
forever, waiting for user input as gui apps will do, and the test
would timeout.
We'd need to add something like:
- --configure --generate and --exit command line
Testing: You can launch the gui from the command line by passing the absolute
path to the executable inside the app bundle:
509:[mjack...@ferb:CMake]$ /private/tmp/CMake-2.8.3/CMake\
2.8-3.app/Contents/MacOS/CMake\ 2.8-3
Qt internal error: qt_menu.nib could not be loaded. The .nib file should
Exactly. It needs further work.
I'm not about to be the brave volunteer who adds a test that adds the
window server must be running requirement. And whoever does should
probably add a setting CMAKE_ENABLE_GUI_TESTS that is OFF by
default. Then, only on dashboard machines that explicitly say they
On 1/5/2011 1:01 PM, David Cole wrote:
Exactly. It needs further work.
I'm not about to be the brave volunteer who adds a test that adds the
window server must be running requirement. And whoever does should
probably add a setting CMAKE_ENABLE_GUI_TESTS that is OFF by
default. Then, only on
On 05.01.11 12:34:09, David Cole wrote:
cmake-gui needs some further work to be automatically testable.
If we launched it as-is on a test run, then it would just hang there
forever, waiting for user input as gui apps will do, and the test
would timeout.
There are also tools out there to
___
Mike Jackson www.bluequartz.net
Principal Software Engineer mike.jack...@bluequartz.net
BlueQuartz Software Dayton, Ohio
On Jan 5, 2011, at 2:01 PM, Bill Hoffman wrote:
On 1/5/2011 1:01 PM,
12 matches
Mail list logo
