Windows support

[mp4096]

Most of the people I know use Windows for writing LaTeX. So it is imperative indentex has first-class Windows (7+) support.

Blocking issues:

• Use termcolor instead of ansi_term -- resolved (by removing colours altogether) in Remove ansi_term and colored output #20
• Compiling with MSVC so that indentex can be packed to a Windows installer together with C++ redistributable -- resolved in Static linking of CRT for Windows #26
• Create a Windows installer, probably using Wix. -- done by @syxolk in Use wix toolset to package windows installer #28
• Do some AppVeyor Config-Fu to auto-deploy on tagged releases

[syxolk]

Compiling with MSVC so that indentex can be packed to a Windows installer together with C++ redistributable

I've just found a configuration that works:

1. Install the Build Tools für Visual Studio 2017
2. Install rustup
3. Use the stable-x86_64-pc-windows-msvc toolchain

[mp4096]

Great!

[syxolk]

... together with C++ redistributable

One can also use the linker flags /MT or /MTd to statically link the standard libraries. At least for an older project of mine the C++ Redistributable was no longer needed. However, I don't know how to do this in rust.

[mp4096]

This would be so awesome if it works: rust-lang/libc#290

[mp4096]

Ok, we'll probably need to bump Rust version to 1.14 in order to support static linking of CRT.

See release notes for 1.14

[mp4096]

I hope this will work for Win 7. MS CRT is relatively new

[syxolk]

Stuff regarding the Wix installer:

• Icons for the installer and the executable
• Banner image for the installer
• Install directory (Program files or AppData)
• Add to PATH (user or system environment variables)
• How to update the version in the wxs file
• How to generate RTF from LICENSE.md (pandoc -f markdown -t rtf LICENSE.md -s -o LICENSE.rtf)

[mp4096]

Banner image for the installer

A blue to black gradient with a bold-italic caption

Install directory (Program files or AppData)

AppData only, no option for system-wide installs.

Add to PATH (user or system environment variables)

Yep.

How to update the version in the wxs file
How to generate RTF from LICENSE.md (pandoc -f markdown -t rtf LICENSE.md -s -o LICENSE.rtf)

I think the best way is to write a release script which does all this stuff automatically.

[syxolk]

https://github.com/syxolk/indentex/tree/wix-packaging

• Install to %LOCALAPPDATA%
• No UAC
• Add install path to user's %PATH%

[mp4096]

Great!

Erm, how are we supposed to generate a GUID (ProductUpgradeCode)? Just take a random number and pray it's not already used?..

[syxolk]

I don't know about the component's GUID but the UpgradeCode must be unique.

http://wixtoolset.org/documentation/manual/v3/howtos/general/generate_guids.html

[mp4096]

Ok, I see. Thanks!

We still have to find out how to link CRT statically. I'll make a separate issue for it.

[mp4096]

After studying RFC 1721, I think that static linking can be enforced by passing a target-feature=+crt-static flag to rustc.

Hence, we need to call cargo like this:

RUSTFLAGS='-C target-feature=+crt-static' cargo build --release --target x86_64-pc-windows-msvc

[mp4096]

🙄

error: failed to run rustc to learn about target-specific information

[mp4096]

Continued in #31