-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(bundler): support custom sign command on Windows #9902
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like you need to run cargo fmt
and cargo clippy -- -Dwarnings
done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it needs to be modified here.
@amrbashir Could you please take a look at it?
@@ -68,6 +67,7 @@ pub fn bundle_project(settings: &Settings, updater: bool) -> crate::Result<Vec<P | |||
let nsis_toolset_path = tauri_tools_path.join("NSIS"); | |||
|
|||
if !nsis_toolset_path.exists() { | |||
create_dir_all(&nsis_toolset_path)?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Creating an NSIS folder in advance will cause subsequent renaming failures after extract
rename(_tauri_tools_path.join("nsis-3.08"), nsis_toolset_path)?;
@amrbashir any thoughts on when v1.7 would be released that contains this fix? |
I don't want to make promises but hopefully this week |
@amrbashir I see 1.7 came out, but I don't see anything about this feature in the release notes, is it indeed in there? |
Maybe a silly question, but I have tauri updated to 1.7.1 (and tauri-build updated to 1.5.3) so everything appears to be updated to latest, but I cannot build with "signCommand".
Anyone know why? |
make sure to also update the CLI |
feat: Migrate v2 functionality to v1.x: support custom sign command on Windows (Discussed in #9900)