I am trying to understand the steps below: Where would the pbk => pbj compilation take place ? Where would the pbj be stored after the build , if the build does not occur on the CI? Will the pbj be compiled by Jenkins ? or built manually and stored somewhere ?
Thanks, Maurice -----Message d'origine----- De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 11 décembre 2013 22:49 À : dev@flex.apache.org Objet : Re: PixelBender and Builds.a.o It is probably worth waiting for response from Justin. Any volunteers to do the work? I think the steps are: 1) copy the pbk files somewhere (flex-utilities repo?) 2) setup build for them 3) create release candidate 4) hold vote. 5) put up candidates on dist 6) change the sdk builds to use the packages on dist -Alex On 12/11/13 1:02 PM, "Maurice Amsellem" <maurice.amsel...@systar.com> wrote: >Agree with the upstream package. Sounds like a good solution, and >rather easy to put in place. > >Maurice > >-----Message d'origine----- >De : Alex Harui [mailto:aha...@adobe.com] Envoyé : mercredi 11 décembre >2013 20:10 À : dev@flex.apache.org Objet : PixelBender and Builds.a.o > >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. > >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? > >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. > >Thoughts? >-Alex >
