flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: 4.16.0 Windows Install issues (was Re: [ANNOUNCE] Apache Flex 4.16.0 released)
Date Tue, 21 Mar 2017 16:48:41 GMT
Can you explain in more detail what steps you would take?

Thanks,
-Alex

On 3/20/17, 1:30 PM, "omuppi1@gmail.com on behalf of OmPrakash Muppirala"
<omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:

>We could do a patch release that does not add any new feature for the 64
>bit installer binary.
>
>We would need to bump up the version so that the auto update functionality
>would be triggered.
>
>In this we probably don't even need a source release as we will only be
>modifying the convenience binaries.
>
>Thanks,
>Om
>
>
>On Mar 20, 2017 11:00 AM, "Alex Harui" <aharui@adobe.com> wrote:
>
>Renaming thread.  On next post I will drop the [ANNOUNCE] tag so we don't
>fill the inboxes of those using an Announce filter.
>
>So, I have heard back from my internal contacts.  There is no plan to
>allow the packaging of a 64-bit app the way we package the 32-bit
>Installer.  Essentially, that means that we have to write our own
>installer for the 64-bit Apache Flex SDK Installer.
>
>Also, the much larger size of AIR 25 is intentional.  There is a feature
>called "bitcode" that is responsible for the increase in size.
>
>Here are some possible solutions, of which we don't have to choose just
>one:
>1) New Installer release.  Try to add the call to clear() and maybe
>rewrite the way we do MD5 checking to not suck in the entire file at once.
> We are overdue for an Installer release.  We really should replace the
>way we get the mirror data with a JSON call.  But on the other hand, that
>will take us several days or weeks to do this, and I'd rather do other
>things.  But if volunteers can step up to do this, that would be great.
>It just won't solve the problem in the short term.
>
>2) Remove AIR 25 from the list of choices until we do #1
>
>3) Make the 64-bit version of the installer available as a zip file.
>Folks would have to download it, unpack it and run it instead of the usual
>installer.
>
>4) Add the installation of the 64-bit installer to the 32-bit Installer!
>I don't know for sure if we can do that, but we should be able to script
>the downloading and unpacking described in #3.
>
>Note that both #3 and #4 would probably not be official Apache releases.
>The 3.2 build script doesn't create a bundle, it only creates an installer
>EXE which will be 32-bit.  Usually, the binary artifact is the result of
>running the build script.  In order to create the 64-bit bundle, I had to
>tweak the build script which effectively changes the source package.  In
>order to do #4, we'd have to create the installer.xml for it.  So, we
>would not replace the existing 3.2 release or deploy the zip on the
>mirrors.  We'd have to host the zip somewhere else, more like making
>nightly builds available to those having problems.
>
>Thoughts?
>-Alex
>
>On 3/19/17, 10:02 PM, "Alex Harui" <aharui@adobe.com> wrote:
>
>>An update:  I was able to generate a 64-bit bundle, but not an installer
>>EXE that installs a 64-bit app.  It seems to generate a 32-bit app.
>>
>>Has anyone seen any info on creating an installer EXE for a 64-bit app?
>>I'll ask internally at Adobe as well.
>>
>>Thanks,
>>-Alex
>>
>>On 3/18/17, 9:33 PM, "Alex Harui" <aharui@adobe.com> wrote:
>>
>>>I haven't tried clear().  I'm trying to see if 64-bit will work because
>>>then I think we can just deploy a new binary instead of having to go
>>>through an entire release process.
>>>
>>>I spent some time this afternoon and could not get the AIR 25 SDK Beta
>>>with 64-bit support to actually generate a 64-bit exe.  Has anyone seen
>>>any documentation on the process?
>>>
>>>Thanks,
>>>-Alex
>>>
>>>On 3/18/17, 8:17 AM, "Josh Tynjala" <joshtynjala@gmail.com> wrote:
>>>
>>>>I wonder if it would help to call clear() on the URLLoader's ByteArray
>>>>in
>>>>the Get AntOnAIR task after we save it to a file. While it's supposed
>>>>to
>>>>be
>>>>GCed eventually, clearing the memory immediately is probably a good
>>>>idea
>>>>with these large files. I've had succuss doing something similar in
>>>>cases
>>>>where BitmapData used too much cumulative memory before it could be
>>>>GCed.
>>>>
>>>>- Josh
>>>>
>>>>On Mar 18, 2017 7:24 AM, "Alex Harui" <aharui@adobe.com> wrote:
>>>>
>>>>> Do any of the Windows platforms we support not handle 64-bit apps?
>>>>> Windows Server 2008 for example?
>>>>>
>>>>> Otherwise, it seems like we should rebuild the Windows Installer on a
>>>>> 64-bit AIR version and replace the 32-bit one that we've deployed?
>>>>>
>>>>> Thoughts?
>>>>> -Alex
>>>>>
>>>>> On 3/17/17, 3:46 PM, "piotrz" <piotrzarzycki21@gmail.com> wrote:
>>>>>
>>>>> >Hi :),
>>>>> >
>>>>> >Can someone post also this information to our Facebook fan page ?
>>>>> >
>>>>> >Thanks,
>>>>> >Piotr
>>>>> >
>>>>> >
>>>>> >
>>>>> >-----
>>>>> >Apache Flex PMC
>>>>> >piotrzarzycki21@gmail.com
>>>>> >--
>>>>> >View this message in context:
>>>>> >https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2Fapache-fle
>>>>> >x-development.2333347.n4.nabble.com%2FANNOUNCE-Apache-
>>>>> Flex-4-16-0-released
>>>>> >-tp60427p60557.html&data=02%7C01%7C%7C526823ea8c5e49aa413108d46d88
>>>>> 85d2%7Cf
>>>>> >a7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636253880511588257&sdata=
>>>>> VGA%2B5
>>>>> >OrpJvyyOLnKX9G4wEv587gNa%2Fa4NInd9G0Auuk%3D&reserved=0
>>>>> >Sent from the Apache Flex Development mailing list archive at
>>>>>Nabble.com.
>>>>>
>>>>>
>>>
>>

Mime
View raw message