-
Notifications
You must be signed in to change notification settings - Fork 2.7k
building an installer #1326
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
Comments
Absolutely!
Somebody changes that to
I think it tries to include the documentation wholesale. I am not sure why that file is missing for you... For me, it is there, and it is owned by the $ pacman -Qo /mingw64/share/doc/git-doc/technical/api-builtin.html
/mingw64/share/doc/git-doc/technical/api-builtin.html is owned by mingw-w64-x86_64-git-doc-html 2.14.2.2.34c1a976dc-1 Is that package not installed for you? |
Didn't know about pacboy. Seems a useful wrapper Wiki edited After update git-doc-html a couple of times (I still see a warning about that api-builtin.html once) now installer is running again I install with it but I still get an error running a git-bash.exe after that
I see that you have a fork of p7zip. I have standard installed on my system. Maybe PATH is forcing my system to use the standard one?. One thing I notice is that your installer can be opened with my 7zip GUI manager but I cannot open the installer generated by me "cannot open file as a compressed file", so I guess there's some problem at the end of installer package that do not execute that post-install commands too. |
Thank you!
As I said elsewhere (can't find it right now), this should be performed by the Maybe that Otherwise, you could simply change the location of that log file in For the record, all of those |
I didn't found many answers looking at post-install.log. I found an app able to extract contents of my installer (yours can be open with 7zip), InnoExtractor. I will compare installers and see what is different |
First thing comparing both installers
That's why post-install crashes I guess |
To expand a variable Windows cmd interpreter requires variable name to be enclosed in percent characters (%), not prefixed with just one. post-install.bat: Version test had always been true, which resulted in rebase being done on *all* 32-bit Windows versions, not only version 10 and above (as was intended). setup-git-sdk.bat: The same side effects as for post-install.bat. Signed-off-by: Jacob Becker <[email protected]>
I think this solves it git-for-windows/build-extra#160 No more sslbackend errors or commands at git-bash.exe initialization |
I set finally
Don't know what's the problem about %ver% being empty. |
I have modified git-for-windows/build-extra#160 after talk with @plastikat. Still don't know the underlying problem, but this seems a correct fix on my system (as %ver% and if evaluates correctly) |
I guess we just forgot to close this ticket ;-) |
Setup
Windows 10 64 bits
What options did you set as part of the installation? Or did you choose the
defaults?
Yes
to the issue you're seeing?
I'm building an installer
Details
C:\Users\afanjul\Desktop\Git SDK 64-bit.lnk
Minimal, Complete, and Verifiable example
this will help us understand the issue.
An installer is made
URL to that repository to help us with testing?
This is not related to specific repository
From lessons learned on git-for-windows/build-extra#148 I want to ask few questions
In wiki about create an installer it should be clearly point out you need to use Git SDK 64-bit.lnk (like in wiki page build git) it's not obvious. Can I do that?
I have updated /usr/src/build-extra and /usr/src/git. Why it is asking for an api-builtin.html? is something removed and should I propose a PR on build-extra
The option to install default git package (when you want to modify things only in build-extra
$ pacman -S mingw-${ARCH}-git
should be added too to wiki, isn't it?
All this ideas try to ease contributions for others. Any other ideas (that just take time and is not done for that reason) please comment here to see how we can get it done
The text was updated successfully, but these errors were encountered: