Mono 3.2.8 确定性构建实现方案咨询

Great question—dealing with non-deterministic builds can be super frustrating, especially when you need consistent checksum values for validation or deployment. Let’s walk through practical workarounds since Mono 3.2.8 doesn’t have the built-in deterministic flag that Mono 4+ offers.

Root Cause Recap #

As you noted, the ECMA 335 standard requires compilers to generate two dynamic values that break build consistency:

• Time-date stamp: Embedded in the PE file header, tied directly to the exact moment you run the build.
• MVID (Module Version Identifier): A unique auto-generated GUID stored in the assembly metadata, which changes every time you compile.

Workaround 1: Fix the MVID Manually #

You can hardcode a fixed MVID in your project to eliminate this variable entirely:

1. Open or create an AssemblyInfo.cs file in your project (if you don’t already have one).
2. Add a line to explicitly set the MVID using a static GUID. For example:

   [assembly: System.Reflection.ModuleVersionId(System.Guid.Parse("12345678-1234-1234-1234-1234567890AB"))]
   

3. Commit this file to your repo so every build uses the same GUID.

This works because the compiler will respect your manually specified MVID instead of generating a new one each time. Just pick a GUID and stick with it—no need to change it unless you intentionally want a new module ID.

Workaround 2: Override the PE Time-Date Stamp #

Mono 3.2.8 doesn’t let you disable the dynamic time-stamp during compilation, but you can modify it post-build:

• Build a small fixer tool: Write a simple utility (in C# or even bash) that edits the PE file’s header to replace the dynamic time-stamp with a fixed value. The time-stamp lives in the IMAGE_FILE_HEADER section as a 4-byte unsigned integer, representing seconds since January 1, 1970.
• Automate the step: Add this tool to your build script (like a Makefile or bash script) so it runs right after compilation. For example:

  # First compile the project
  mcs /out:MyApp.exe MyApp.cs AssemblyInfo.cs
  
  # Run your time-stamp fixer tool
  mono FixTimeStamp.exe MyApp.exe --fixed-timestamp 1600000000
  

A quick heads-up: Always back up your compiled binaries before modifying them, and test the edited file thoroughly to make sure it still runs correctly.

Workaround 3: Combine Both Steps in an Automated Pipeline #

For full consistency, wrap both fixes into your build workflow:

1. Ensure your AssemblyInfo.cs has a fixed MVID.
2. Compile the project with mcs as usual.
3. Run your post-build tool to set a fixed time-stamp in the PE header.

This way, every build will spit out an identical binary with consistent checksum values.

Key Notes to Remember #

• Hardcoding the MVID is safe for most apps—only avoid it if your code relies on the MVID for specific logic (like module version tracking).
• Modifying the PE header is a low-level workaround, so don’t skip testing the modified binary.
• These are temporary fixes—upgrading to Mono 4+ (or newer) is the long-term solution since it includes official deterministic build support, but we get that’s not feasible right now.

内容的提问来源于stack exchange，提问作者Sixx