Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support x64 and ARM64 bundles #4579

Closed
wixbot opened this issue Nov 3, 2014 · 4 comments
Closed

Support x64 and ARM64 bundles #4579

wixbot opened this issue Nov 3, 2014 · 4 comments
Assignees
Milestone

Comments

@wixbot
Copy link

wixbot commented Nov 3, 2014

Hi,

the windows server core operating system popularity is increasing, mostly on the storage and compute(data centers ) companies which want to use thin OS.
The demand for supporting a native 64 bit setup increased.
We received requests for it for some of our biggest clients.

Thanks, in advance

Lior

Originally opened by liorby

@wixbot
Copy link
Author

wixbot commented Nov 13, 2014

This impacts engine and also balutil, WixStdBA, and managed BA support. At least for v4.0, we should resolve the breaking change to support x64 in the engine and toolset.

Release changed from v3.9 to v4.0

@wixbot wixbot added this to the v4.0 milestone Dec 20, 2015
@Danielku15
Copy link

One more reason to support x64 bootstrappers is the use of external libraries in your Managed BA. We have some native libraries build in x64 and wrapped via managed C++. We need to use this libraries in our custom BA wizard. Calling x64 managed C++ libraries from a x86 BA will obviously fail with a BadImageFormatException.

@SaradaKantheti
Copy link

Several new products which are going azure and dependent on wix are mostly x64applications. We are using wix v3.11 and need to test our 64- bit binaries using wix64-bit bootstrapper applications. In this regard we need to know whether the above issues are fixed and backported to 3.11? If so, please provide us with the sample test applications. Building 64-bit bootstrapper is critical to our customers, please provide us with the fix as soon as you can.

@rseanhall
Copy link
Contributor

We do not intend on adding any new features to v3.x.

This issue is open and unassigned. That means it is waiting for someone to implement the feature. We have put it into the v4.0 milestone so it will be there by the time v4.0 ships.

If you are interested in implementing this yourself, our developer documentation provides a great checklist for getting started. Otherwise, you'll want to consider how to motivate others to implement it for you in your desired timeframe. This is a pretty good list of support options.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

5 participants