On 12/11/13 11:25 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>On Wed, Dec 11, 2013 at 11:09 AM, Alex Harui <aha...@adobe.com> wrote: > >> Thanks to Maurice, we have a pretty good idea of why Jenkins on >>builds.a.o >> is not able to build the Flex SDK. Unfortunately, it isn't clear that >> infra knows how to fix it or can fix it given how they want to run that >> server. >> > >I will give Gavin a day or so and then ping him again. I think we should >be able to get a fix for this soon. Well, if he wants to run Jenkins as a service, is there really a fix? I'm thinking that we should change our packaging so he doesn't have to deal with this. > > >> >> Meanwhile, I'm still trying to get access to the PB compiler source, but >> one person I talked to said that Alchemy-based shaders will outperform >>PB >> shaders. So, one potential way to solve this problem is to replace our >> shaders with Alchemy shaders. I have no idea how hard that would be. >> Anybody think they can do it quickly? >> > >It should be possible, but that quickly removes FP 10.2, 10.3 and AIR >2.6,27 from the supported runtimes list. Alchemy/FlasCC is supported only >FP 11.0/AIR 3.0 and up [1]. Is this something we want to do? >From an enterprise support point of view, keeping support for 10.2 and >10.3 >can only benefit us. I wouldnt want to give this up for a few shaders. OK. > > >> >> Another option, which is a variant of what Maurice was proposing >>yesterday >> is that we quickly create an official release package that contains just >> the PBK files. Then the corresponding convenience binary package would >> have the PBJ files. We call this an upstream package that only is >> supported on Mac and Win. We would not use CI for this release. >> >> Then we adjust the SDK build to use this upstream package. This is make >> more official the workaround we are using for Linux and bring Linux up >>to >> par with Mac and Win. Yes, the installer has to change as well, but >> hopefully I'll have new installer capability ready shortly anyway that >> should make it easier for us to make these changes. >> > >Works for me. We have not changed the pbk files forever, yet we keep >compiling them everytime and run into issues like these often. BTW, we >already have a job on builds.apache.org that does this [2] I assume this job would fail if it ever ran again? -Alex
