Felipe, Good suggestion. By making it a compiler option, it could be unchecked if you don't want the default barebones app bundle to be created. For experienced developers, this would probably be what they would want since they would probably have to delete the barebones app bundle in order to use their own Info.plist, etc.
However, by making it on by default, it would mean that new developers wouldn't have to worry about figuring this out. Thanks. -Phil -----Original Message----- From: Felipe Monteiro de Carvalho [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 3:04 AM To: lazarus@miraclec.com Subject: Re: [lazarus] Debugger on Mac OS X On 5/31/07, Hess, Philip J <[EMAIL PROTECTED]> wrote: > I think you can set Pass Options To The Linker to this: > > -framework carbon -framework Qt4Intf -lobjc > > for each new project and then just forget about it. You can then change > the widget type to gtk, qt or carbon as needed and compile. I don't > believe the extra linker switches make any difference if not needed to > resolve references for a particular widget set. In this case we could add a new compiler option, that only works on Mac OS X, similar to the compiler option to create a windows GUI app. And this option would be on by default on graphical application. Lazarus would ignore it when not in mac os x. -- Felipe Monteiro de Carvalho _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives _________________________________________________________________ To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives
