Re: [AD] Next steps

[Peter Wang <novalazy@xxxxxxxxxx>]

I finally wrote such a script instead of waiting for someone else to do
it.  At least we can build most Allegro examples now, even if most won't
run correctly yet.

I haven't figured out how files work.  Help getting a few more examples
running would be appreciated, e.g. a5teroids.


On Mon, 28 Oct 2013 08:29:22 -0600, Trent Gamblin <nooskewl@xxxxxxxxxx> wrote:
> I don't see any way around it, or a real problem with it. The only way to 
> change that is to write some script or makefile but it would have to be 
> tailored to the user's system - so no real benefit.
> 
> Trent
> 
> -----Original Message----- 
> From: Peter Wang
> Sent: Monday, October 28, 2013 7:38 AM
> To: Trent Gamblin
> Cc: Allegro Development
> Subject: Re: [AD] Next steps
> 
> On Sat, 26 Oct 2013 23:25:43 -0600, Trent Gamblin <nooskewl@xxxxxxxxxx> wrote:
> > I think all of that is pretty OK.
> >
> > - iOS should be ok
> > - Android is ok
> > - Touch input is good -- but I can't test it on Windows
> >
> > Let me know if you want me to do anything specifically.
> 
> Thanks.
> 
> How should a user ultimately use the Android port?  With other ports you
> can just run make install and then link with the library.  The Android
> port seems too special, with its specific directory structure and fiddly
> files, and confusing (for a C programmer) Android build tools.
> 
> Maybe we need some big changes or only a few tweaks, but I don't know
> what we should be aiming for.
> 
> Peter 
>