The actual code has not been approved for public release but I am trying to 
narrow it down to a workable example.
  The one thing I have discovered is that I have a function where I build up 
the app and all the supporting calls to fixup bundle and all that setup stuff. 
I pass in the source files, name of the executable, libraries, search dirs, 
plugins and all that sort of stuff. It is within that function that I set all 
the variables then call add_executable.

  Now, if I set all the cmake variables BEFORE I call my function then I get a 
valid plist file. Would this type of combination have anything to do with it? 
Or just a red herring? I was able to reproduce the issue a few times on my 
system so there _is_ some sort of interaction there.
___________________________________________________________
Mike Jackson                      www.bluequartz.net
Principal Software Engineer       mike.jack...@bluequartz.net 
BlueQuartz Software               Dayton, Ohio

On Feb 10, 2011, at 2:39 PM, David Cole wrote:

> Can you share your source code so I can repro the issue here?
> 
> Thx,
> David
> 
> 
> On Thu, Feb 10, 2011 at 2:25 PM, Michael Jackson 
> <mike.jack...@bluequartz.net> wrote:
> 
> On Feb 10, 2011, at 2:04 PM, David Cole wrote:
> 
> > On Thu, Feb 10, 2011 at 1:51 PM, Bill Hoffman <bill.hoff...@kitware.com> 
> > wrote:
> > On 2/10/2011 1:27 PM, Michael Jackson wrote:
> > Bump?
> >
> > Did you try cmake --trace to see when it was configure...
> >
> >
> > --
> > Mike Jackson<www.bluequartz.net>
> >
> > On Feb 8, 2011, at 5:36 PM, Michael Jackson wrote:
> >
> > At what point is the MacOSXBundleInfo.plist.in configured? I am setting all 
> > the relevant variables but they are not getting inserted into the plist.
> >
> > Here is some debug output from a CMake run of my project:
> >
> > -- MACOSX_BUNDLE_INFO_STRING: StatsGenerator_debug Version 2011.02.08, 
> > Copyright 2009 BlueQuartz Software.
> > -- MACOSX_BUNDLE_ICON_FILE: StatsGenerator.icns
> > -- MACOSX_BUNDLE_GUI_IDENTIFIER: StatsGenerator_debug
> > -- MACOSX_BUNDLE_LONG_VERSION_STRING: StatsGenerator_debug Version 
> > 2011.02.08
> > -- MACOSX_BUNDLE_BUNDLE_NAME: StatsGenerator_debug
> > -- MACOSX_BUNDLE_SHORT_VERSION_STRING: 2011.02.08
> > -- MACOSX_BUNDLE_BUNDLE_VERSION: 2011.02.08
> > -- MACOSX_BUNDLE_COPYRIGHT: Copyright 2011, BlueQuartz Software. All Rights 
> > Reserved.
> >
> >
> > I set all those variables before and after the add_executable call but most 
> > of the values does not show up in the plist file. Probably something simple 
> > I am missing.
> >
> > Thanks.
> > ___________________________________________________________
> > Mike Jackson                      www.bluequartz.net
> > Principal Software Engineer       mike.jack...@bluequartz.net
> > BlueQuartz Software               Dayton, Ohio
> >
> >
> > Does your add_executable call have the MACOSX_BUNDLE flag in it?
> >
> > You should definitely set those variables before calling add_executable, 
> > and they should definitely show up if you have MACOSX_BUNDLE turned on.
> >
> > What generator are you using? Xcode or Unix Makefiles or something else?
> >
> >
> 
> Using Makefiles generator. Correctly set MACOSX_BUNDLE in the 
> add_executable() call. This is on OS X 10.6.6 with CMake 2.8.3 (self compiled)
> 
> I tried the --trace but I don't really know what I should be looking for. 
> There is a lot of output to look through.
> 
> Tried from a clean build directory and still has the same thing.
> 
> Mike Jackson
> 
> 
> 
> _______________________________________________
> 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 CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake
> 

_______________________________________________
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 CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to