Lucas and David,

Thank you for your responses.

*Does anything get printed in the terminal if you type and enter: *
*/Applications/MyApp.app/Contents/MacOS/MyApp**?*

This is what I mean when I say I can run it through the terminal.  If I
enter the above command the app starts properly.

*Does your app launch a lot of sub-processes at startup?*

Nope - and as far as I can tell the code in my main.cpp isn't even reached.


*Are you saying that you *can* run the app from the terminal window, but
that you cannot run the app by double-clicking or by using "open"? (And
that it's the exact same executable...?) What command line do you use if
you're not using "open"?*
That's correct.  I use the command described in the first response.

*Is there an environment difference (maybe LD_LIBRARY_PATH or
DYLD_LIBRARY_PATH?) between your Terminal, and your overall environment?*

Not that I can tell.

*Can you launch a debug build in a debugger?*

Building in debug mode doesn't seem to make any difference.

The fundamental problem seems to be whatever the open command does in the
background, I haven't set things up properly in terms of open knowing that
the when I run open MyApp.app, it should run
MyApp.app/Contents/MacOS/MyApp.  I've got CFBundleExecutable set to
MyApp... in fact my .plist looks like this:

<?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>MyApp</string>
<key>CFBundleIdentifier</key>
<string>com.MyApp</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string> MyApp</string>
<key>CFBundleIconFile</key>
<string> MyApp</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>2.1.0</string>
<key>CFBundleVersion</key>
<string>2.1.0</string>
<key>CSResourcesFileMapped</key>
<true/>
<key>LSRequiresCarbon</key>
<true/>
<key>NSHighResolutionCapable</key>
<true/>
</dict>
</plist>

Again, not sure how to proceed.  But, I really appreciate the help.

Regards,
Scott


On Mon, Jun 23, 2014 at 6:13 AM, David Cole <dlrd...@aol.com> wrote:

> Also, you may find extra hints about what's going wrong in the output of
> the "Console" application. (Usually found in "/Applications/Utilities") --
> see if there's anything in the "system.log" in there, or poke around and
> see if it has a crash report related to your app.
>
>
> HTH,
> David C.
>
>


-- 
Scott Klum
B.S. in Computer Science, Michigan State University 2012
M.S. in Computer Science, Michigan State University 2014
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Reply via email to