This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Legacy Flash implementation (was: Re: Build fails after CVS update)
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Rutger Hofman <rutger at cs dot vu dot nl>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Sun, 8 Jul 2007 20:57:36 +0200
- Subject: Re: [ECOS] Legacy Flash implementation (was: Re: [ECOS] Build fails after CVS update)
- References: <46851C3D.5000400@cs.vu.nl> <46851F7A.8010709@mlbassoc.com> <46852457.5080601@cs.vu.nl> <468E1AE7.6050605@cs.vu.nl>
On Fri, Jul 06, 2007 at 12:35:19PM +0200, Rutger Hofman wrote:
> Rutger Hofman wrote:
>>> Rutger Hofman wrote:
>>>> I updated to the most recent version of the CVS list; the previous
>>>> checkout was from last february, not too long ago; but I ran into some
>>>> problems:
>>>>
>>>> = the Legacy Flash stuff has disappeared, but I use it (I think I might
>>>> be the only user, but still!).
>
>> The ... problem is with the flash stuff. The "Legacy API" flash ... won't
>> compile.
>> What is the best way to tackle this? What is the quickest way to tackle
>> this? I don't really want to port our vendor's flash implementation to the
>> newer flash implementation. Is there a way that I can easily restore the
>> legacy API stuff?
>
> A week ago, I asked this. I think it has escaped the attention of the list.
Sorry, been away.
I need more details. I don't see anything in the ChangeLogs about
removing the Legacy API.
Do you know which change caused the problem? What exactly is the
problem you are having now?
Thanks
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss