The dynamic library path is empty. Yep, the stuff I posted is just a snippet, this is the full file (minus some file type associations):
#################################### <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleExecutable</key> <string>paraview</string> <key>CFBundleGetInfoString</key> <string></string> <key>CFBundleIconFile</key> <string>MacIcon.icns</string> <key>CFBundleIdentifier</key> <string></string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleLongVersionString</key> <string></string> <key>CFBundleName</key> <string>ParaView</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string></string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string></string> <key>CSResourcesFileMapped</key> <true/> <key>LSRequiresCarbon</key> <true/> <key>NSHumanReadableCopyright</key> <string></string> <!-- File type associations --> <key>CFBundleDocumentTypes</key> …more stuff here... </dict> </plist> #################################### I don't see any differences to what you've written, so I really don't know what to make of it. Michael On May 31, 2013, at 17:17 , Pat Marion wrote: > Hmm, no I don't know what would cause that. By any chance, have you set the > DYLD_LIBRARY_PATH environment variable? If so, try unsetting that. I assume > the lines you pasted from the Info.plist is just a snippet, and the file > contains more than that, right? > > > <?xml version="1.0" encoding="UTF-8"?> > <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" > "http://www.apple.com/DTDs/PropertyList-1.0.dtd";> > <plist version="1.0"> > <dict> > <key>CFBundleDevelopmentRegion</key> > <string>English</string> > <key>CFBundleExecutable</key> > <string>paraview</string> > <key>CFBundleGetInfoString</key> > <string></string> > <key>CFBundleIconFile</key> > <string>MacIcon.icns</string> > <key>CFBundleIdentifier</key> > <string></string> > <key>CFBundleInfoDictionaryVersion</key> > <string>6.0</string> > <key>CFBundleLongVersionString</key> > <string></string> > <key>CFBundleName</key> > <string>ParaView</string> > <key>CFBundlePackageType</key> > <string>APPL</string> > <key>CFBundleShortVersionString</key> > <string></string> > <key>CFBundleSignature</key> > <string>????</string> > <key>CFBundleVersion</key> > <string></string> > <key>CSResourcesFileMapped</key> > <true/> > <key>LSRequiresCarbon</key> > <true/> > <key>NSHumanReadableCopyright</key> > <string></string> > > <!-- File type associations --> > <key>CFBundleDocumentTypes</key> > <array> > > ....snip... > > <!-- File type associations --> > > </dict> > </plist> > > > On Fri, May 31, 2013 at 3:15 AM, Michael Schlottke > <m.schlot...@aia.rwth-aachen.de> wrote: > Hi Pat, > > If I do that, I get an error "The application cannot be opened because its > executable is missing.". When I have a look at the Info.plist file, it > contains the lines > > <key>CFBundleExecutable</key> > <string>paraview</string> > > and <builddir>/bin/paraview.app/Contents/MacOS has a "paraview" executable. > Any idea what the reason could be? > > Michael > > P.S.: As I already noted on "Paraview-developers] Problems with protobuf when > loading self-compiled plugin on OS X", I cannot use "make install" to create > a working app bundle in the /Applications directory. If I use "make install", > I *am* able to start ParaView using the "open" command, but then I buy this > convenience with losing the ability to use my own plugins. I don't know if > this makes a difference or not - as far as I understand from the ParaView > build wiki, I should be able to use ParaView without using "make install" > > On May 30, 2013, at 22:12 , Pat Marion wrote: > >> Hi Michael, >> >> That's a standard behavior of MacOSX. If you start the application with >> "open bin/paraview.app" then the window will appear on top. >> >> Pat >> >> >> On Thu, May 30, 2013 at 10:38 AM, Michael Schlottke >> <m.schlot...@aia.rwth-aachen.de> wrote: >> Hi, >> >> I installed ParaView 4.0.0-RC2 on my Macbook by compiling it from source. >> When I start ParaView from command line, it always disappears behind the >> active window. Does anyone know how to fix this, so that when ParaView is >> started, it will be the application at the very front of my screen? Please >> note that is not started "hidden" (i.e. only in the dock), but the window >> actually uses the full screen - it's just not visible and you have to use >> Cmd-Tab to get to it. >> >> Regards, >> >> Michael >> >> >> >> _______________________________________________ >> Powered by www.kitware.com >> >> Visit other Kitware open-source projects at >> http://www.kitware.com/opensource/opensource.html >> >> Please keep messages on-topic and check the ParaView Wiki at: >> http://paraview.org/Wiki/ParaView >> >> Follow this link to subscribe/unsubscribe: >> http://www.paraview.org/mailman/listinfo/paraview >> >> > >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
