-
Notifications
You must be signed in to change notification settings - Fork 152
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
Simplify MSI build process #1432
Comments
@OsirisTerje If you have any thoughts of dropping the msi, however, let me know and I won't bother with this. |
Imho, I would drop the msi. |
IIRC, I dropped it in V4. What about V3? |
Just drop it. |
Will do... closing this one... |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've had to make an number of changes to the platforms we support lately, most recently for issue #1430.
The msi package provides the greatest challenge in getting it right the first (or third or fourth) time. In part that's in the nature of the XML format we have to use, which is very complex. But a large part of the problem seems to stem from the two-step process we use, which is...
IIRC, I created that process many years ago because it seemed "simpler" to me. The problem is that when any thing fails to work, you have to start by figuring out which of the two steps created the problem - and sometimes it's both!
With this issue, I'd like to experiment with making it a one-step process. It seems that know where each file in the image came from, so, in principle, it should be possible to just grab that each file from that location directly in the
.wxi
entries.In any case, I'll give it a go.
The text was updated successfully, but these errors were encountered: