Re: [AD] Two custom mouse cursor patches

["Peter Hull" <peterhull90@xxxxxxxxxx>]

That's not a bad idea to try the generated Xcode project; it would
solve both problems. I'd like to see at least one program built as a
proper bundle though (and I think the demo is the best candidate for
that) Anyone know if cmake knows about bundles? The other issue is
universal binaries, can cmake do that automatically?

On bundles and frameworks, there's nothing magical about them, just
the structure, so you can build an app bundle or framework with mkdir
and cp if you want. You just need an info.plist for the app. The plist
contains the version info, icon name etc.

Frameworks are great for the system libs but IMO less use for 3rd
party apps. It's nice to keep the lib+headers all together (and
versioned), and it works nicely with XCode but for deployment you then
have to install the framework in some System-wide location (breaking
the "drag and drop install" concept) or use embeddable frameworks
which then means you are distributing the Allegro headers alongside
your app, which are useless. Also you to use frameworks you have to
#include <framework-name/header-name> thereby breaking cross-platform
compatibility. The best way, I think, is to static link the library
(and this is what Apple recommend too) Still, if it's what our
'customers' want, we can do it. Finally it seems to me that TH has a
bit of a thing about 'Unix'; he seems allergic to the whole idea of
/usr/local/include and he _is_ very persuasive on a.cc. Frameworks use
the same technology as 'unix' libraries, it's just the packaging is
different.

Pete

On Mon, Sep 15, 2008 at 1:56 PM, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> On 15 Sep 2008, at 08:36, Peter Wang wrote:
>> How are the XCode project files generated by CMake?  I only tried one
>> from the command line with xcodebuild but it seemed to work fine.
>
> That's a good question, actually. I wonder if we can just tell people
> to run CMake to generate the XCode project file and then use that to
> compile? Presumably CMake will take care of setting up the library
> paths that need to be set up, so we don't have to figure out how to
> do this from XCode (CMake will have to set up demo.app though).
> On the other hand, MacOS X users may not like doing that. It's
> probably worthwhile to ask Thomas Harte on a.cc.
>
> Questions related to the Allegro build system on OS X: does Allegro 5
> actually compile as a so-called framework? I have really no idea why
> a framework is useful, but it seems to be the proper way to
> distribute libraries on OS X. Similarly, do we still have the tools
> to make application bundles? Presumably the procedure for doing this
> wouldn't be different from Allegro 4.2.
>
> Evert
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>