Found the problem. Currently in the pqClientDocFinder.txt file you
list the entire path to the QtAssistant executable. Qt is trying to be
_too_ cute and they actually add ".app/Contents/MacOS/assistant" in
the QtAssistantClient.cpp constructor.
In the Applications/Client/CMakeLists.txt file around line 156 you can
add the following:
IF (APPLE)
SET (PV_ASSISTANT "${QT_BINARY_DIR}/bin/assistant")
ENDIF (APPLE)
which "works for me". I have a DyLib build of Qt instead of a
Framework build but should work there also.
I am working on some other fixes for these issues in the mean time.
_________________________________________________
| Mike Jackson - Principal Software Engineer |
| BlueQuartz Software |
| [EMAIL PROTECTED] |
| www.bluequartz.net |
---------------------------------------------------
On Sep 9, 2008, at 1:11 PM, Berk Geveci wrote:
Yup. We noticed the same problem. It is failing on our Mac dashboard.
We will track it down soon.
-berk
On Tue, Sep 9, 2008 at 12:48 PM, Mike Jackson
<[EMAIL PROTECTED]> wrote:
Is the current CVS version of ParaView broken with respect to
launching
QtAssisant? I am on OS X 10.5 (intel) and after a build when I try
to use
the "Help->Launch Assistant" menu I get an error that simply states
"Failed
to start Assistant".
I can't figure out if the paths are wrong or what?
Any help is appreciated.
Thanks
_________________________________________________
| Mike Jackson - Principal Software Engineer |
| BlueQuartz Software |
| [EMAIL PROTECTED] |
| www.bluequartz.net |
---------------------------------------------------
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
_______________________________________________
ParaView mailing list
[email protected]
http://www.paraview.org/mailman/listinfo/paraview
