[TIMOB-23882] Windows: Allow multiple architectures to be targeted when packaging for Windows 10
GitHub Issue | n/a |
Type | Improvement |
Priority | Medium |
Status | Closed |
Resolution | Won't Do |
Resolution Date | 2018-08-15T10:13:10.000+0000 |
Affected Version/s | Release 6.0.0 |
Fix Version/s | n/a |
Components | Windows |
Labels | qe-6.0.0 |
Reporter | Ewan Harris |
Assignee | Kota Iguchi |
Created | 2016-09-09T11:56:00.000+0000 |
Updated | 2019-05-09T06:46:36.000+0000 |
Description
Description
When a Windows 10 application in Visual Studio a developer is given the option to select the architectures they wish to package for, with the options of x86, x64 and ARM. The app is then built for all architectures and a universal app bundle is created.
When a developer packages a titanium application for Windows Platform they will only be able to package for one architecture at a time by choosing either dist-phonestore
or dist-winstore
, this means that in order to create a universal app a developer will have to package multiple times each release cycle, and also will not be able to package for x64 architecture.
I propose that we investigate the following possibilities:
* Add a new packaging option, dist-universal
, when packaging for this it will create an appx that includes all architectures.
** This fits in with the naming scheme of the current options, but is not immediately clear to a user what architectures will be targeted
* Replace the existing dist-*
packaging options with a singular option, and then introduce a flag to allow a user to specify the architectures to be built, either defaulting to all or to prompt the user to select
** This is a much larger effort that although it provides a better publishing flow the cost probably outweighs the benefit
Comments
JSON Source
Unfortunately, after some investigations it turns out this is difficult to implement because we are pretty much depending on
cmake
to generate Visual Studio projects, andcmake
doesn't work well with building apps for multiple architectures all at once. I would resolve this asWon't Do
for now to indicate it is difficult things to do. Once we find new solutions for this, feel free to reopen this ticket.