mozc_tip32.dll build with Bazel is not 32-bit binary

[yukawa]

Description

mozc_tip32.dll build with Bazel is actually 64-bit binary.

This is a regression introduced by de7615f.

The root cause is that --cpu command line option has been ignored since Bazel 7.0.

• incompatible_enable_cc_toolchain_resolution: Turn on toolchain resolution for cc rules bazelbuild/bazel#7260
• Migrating to Platforms

As we still rely on --cpu command line option here, we cannot remove --noincompatible_enable_cc_toolchain_resolution until we fully migrate to --platforms command line option.

mozc/src/win32/installer/transition.bzl

Lines 35 to 53 in 74384fd

	def _win_executable_transition_impl(
	settings, # @unused
	attr):
	features = []
	if attr.static_crt:
	features = ["static_link_msvcrt"]
	return {
	"//command_line_option:features": features,
	"//command_line_option:cpu": attr.cpu,
	}
	_win_executable_transition = transition(
	implementation = _win_executable_transition_impl,
	inputs = [],
	outputs = [
	"//command_line_option:features",
	"//command_line_option:cpu",
	],
	)

Our GYP build is not affected by this issue.

Steps to reproduce

Steps to reproduce the behavior:

1. Build Mozc64.msi
2. dotnet tool run wix msi decompile Mozc64.msi -x dump
3. dumpbin /headers dump\File\mozc_tip32.dll | findstr machine

Expected behavior

14C machine (x86)

Actual behavior

8664 machine (x64)

Version or commit-id

74384fd

Environment

• OS: Windows 11 23H2

[yukawa]

Unfortunately this is regressed again with 6dadef1, which updated Bazel version from 7.4.1 to 8.0.0.

• Migrate to Bazel 8.0 #1118

Looks like Bazel 8.0 removed --noincompatible_enable_cc_toolchain_resolution option, which we have relied on. We definitely need to fully migrate to --incompatible_enable_cc_toolchain_resolution to go forward.