Build/Build kJams script - Revision history

Dave: replace WinAppHelper .app stubs with prlexec .command launchers

2026-09-08T00:22:42Z

replace WinAppHelper .app stubs with prlexec .command launchers

Dave: match 2023 recipe: names, GetInfoString, APP Path; do not change CFBundleIdentifier

2026-09-07T23:27:25Z

match 2023 recipe: names, GetInfoString, APP Path; do not change CFBundleIdentifier

Dave: restore CFBundleIdentifier uniqueness from 2013 recipe; Python creator

2026-09-07T23:04:21Z

restore CFBundleIdentifier uniqueness from 2013 recipe; Python creator

Dave: WinAppHelper stubs belong in Perforce after creating on sugarbear

2026-09-07T22:07:11Z

WinAppHelper stubs belong in Perforce after creating on sugarbear

← Older revision		Revision as of 22:07, 7 September 2026
Line 87:		Line 87:
	That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.		That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.

	taurus-pc must be running. Do not run the script on taurus, pandora, or bobina. ~~The~~ stubs ~~live on sugarbear's disk at~~ <code>~~.../~~xplat/proj/win/_scripts/</code> — ~~that is the path~~ <code>open</code> uses~~. It is not pandora~~'s ~~depot and not a substitute for~~ <code>p4 sync</code> on taurus.		taurus-pc must be running. Do not run the script on taurus, pandora, or bobina. After creating the stubs, copy them into the depot <code>xplat/proj/win/_scripts/</code> tree and '''submit''' — they belong in Perforce. <code>open</code> on sugarbear still uses that host's copy of the same path. Always <code>p4 sync</code> '''taurus''' after submit (self-contained workspace, not pandora's disk).

	Bobina is not scripted: Parallels there is version-locked for luna.		Bobina is not scripted: Parallels there is version-locked for luna.

Dave: add sugarbear WinAppHelper script; keep bobina as manual recipe

2026-09-07T20:31:33Z

add sugarbear WinAppHelper script; keep bobina as manual recipe

← Older revision		Revision as of 20:31, 7 September 2026
Line 76:		Line 76:
	<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.		<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.

	== ~~Recipe~~ (~~one stub~~) ==		== Sugarbear (taurus-pc, scripted) ==

	~~Do this '''on bobina''' (for luna~~-pc~~) or~~ '''on sugarbear''' ~~(for taurus-pc). The Windows guest must be running and logged into the GUI session you want the build to use.~~		The three taurus-pc stubs are created on '''sugarbear''' by:

	# On ~~the hardware host~~, open the Parallels "Windows applications" folder for '''~~that~~''' ~~guest (bobina: luna-pc Applications; sugarbear: taurus-pc Applications)~~.		<pre>
			/bin/bash /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.sh --dry-run
			/bin/bash /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.sh
			</pre>

			That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.

			taurus-pc must be running. Do not run the script on taurus, pandora, or bobina. The stubs live on sugarbear's disk at <code>.../xplat/proj/win/_scripts/</code> — that is the path <code>open</code> uses. It is not pandora's depot and not a substitute for <code>p4 sync</code> on taurus.

			Bobina is not scripted: Parallels there is version-locked for luna.

			== Recipe (bobina / luna-pc, one stub, manual) ==

			Do this '''on bobina''' for <code>Build kJams luna-pc.app</code>. luna-pc must be running and logged into the GUI session you want the build to use.

			# On bobina, open the Parallels "Windows applications" folder for '''luna-pc'''.
	## If you cannot find it: Parallels → Configure → Options → Applications → enable "Show Windows applications folder in Dock". Dock icon → Reveal in Finder.		## If you cannot find it: Parallels → Configure → Options → Applications → enable "Show Windows applications folder in Dock". Dock icon → Reveal in Finder.
	# Copy '''Command Prompt''' to the Desktop.		# Copy '''Command Prompt''' to the Desktop.
Line 91:		Line 106:
	# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path. Confirm <code>VM Name</code> is luna-pc or taurus-pc as appropriate.		# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path. Confirm <code>VM Name</code> is luna-pc or taurus-pc as appropriate.
	# Move the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).		# Move the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).
	# ~~Repeat for each row in the table (four stubs total: one~~ on bobina~~, three on sugarbear).~~		# You only need this once on bobina (<code>Build kJams luna-pc.app</code>). sugarbear's three stubs come from the script above, not from this copy-Command-Prompt list.
	~~# After creating them, add the new bundles to Perforce on the machine where you created them~~ (~~or copy the bundle onto pandora's depot tree and~~ <code>~~p4 add~~</code> ~~there~~).

	== Hop (what taurus actually does) ==		== Hop (what taurus actually does) ==
Line 105:		Line 119:

	* Depot docs: <code>Development/documentation/01_Infrastructure_Overview.md</code>		* Depot docs: <code>Development/documentation/01_Infrastructure_Overview.md</code>
			* <code>Development/xplat/python/create_sugarbear_winapphelpers.md</code>
	* <code>CF/python/xplat.py</code> — <code>guest_to_host()</code>, <code>get_win_build_apphelper_name()</code>		* <code>CF/python/xplat.py</code> — <code>guest_to_host()</code>, <code>get_win_build_apphelper_name()</code>

Dave: remove leftover stub templates; depot keeps only the .bat files

2026-09-07T20:03:21Z

remove leftover stub templates; depot keeps only the .bat files

← Older revision		Revision as of 20:03, 7 September 2026
Line 75:		Line 75:

	<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.		<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.

	Old names that Python no longer opens (leave them until the new stubs exist, then delete): <code>Build kJams Luna.app</code>, <code>Build kJams Taurus.app</code>, <code>code sign Taurus.app</code>, <code>code sign paths Taurus.app</code>, <code>Build kJams Bobina.app</code>, <code>Build kJams Pandora.app</code>, <code>Build kJams.app</code>, <code>code sign.app</code>.

	== Recipe (one stub) ==		== Recipe (one stub) ==

Dave: rename code-sign bats to app/paths; path stub is plural

2026-09-07T19:59:04Z

rename code-sign bats to app/paths; path stub is plural

← Older revision		Revision as of 19:59, 7 September 2026
Line 66:		Line 66:
	\| sugarbear		\| sugarbear
	\| taurus-pc		\| taurus-pc
	\| <code>Z:\depot\kJams\Development\xplat\proj\win\_scripts\~~code_sign_taurus~~.bat</code>		\| <code>Z:\depot\kJams\Development\xplat\proj\win\_scripts\code_sign_app_taurus.bat</code>
	\|-		\|-
	\| <code>code sign ~~path~~ taurus-pc.app</code>		\| <code>code sign paths taurus-pc.app</code>
	\| sugarbear		\| sugarbear
	\| taurus-pc		\| taurus-pc
	\| <code>Z:\depot\kJams\Development\xplat\proj\win\_scripts\~~code_sign_path_taurus~~.bat</code>		\| <code>Z:\depot\kJams\Development\xplat\proj\win\_scripts\code_sign_paths_taurus.bat</code>
	\|}		\|}

	<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.		<code>build.bat</code> picks VS 2019 on <code>LUNA-PC</code> and VS 2022 elsewhere, then runs <code>win_build.py</code>.

	Old names that Python no longer opens (leave them until the new stubs exist, then delete): <code>Build kJams Luna.app</code>, <code>Build kJams Taurus.app</code>, <code>code sign Taurus.app</code>, <code>code sign ~~path~~ Taurus.app</code>, <code>Build kJams Bobina.app</code>, <code>Build kJams Pandora.app</code>, <code>Build kJams.app</code>, <code>code sign.app</code>.		Old names that Python no longer opens (leave them until the new stubs exist, then delete): <code>Build kJams Luna.app</code>, <code>Build kJams Taurus.app</code>, <code>code sign Taurus.app</code>, <code>code sign paths Taurus.app</code>, <code>Build kJams Bobina.app</code>, <code>Build kJams Pandora.app</code>, <code>Build kJams.app</code>, <code>code sign.app</code>.

	== Recipe (one stub) ==		== Recipe (one stub) ==
Line 100:		Line 100:
	* '''Win32 build:''' taurus SSHes to '''bobina''' and <code>open</code>s <code>Build kJams luna-pc.app</code> → luna-pc runs <code>build.bat</code>.		* '''Win32 build:''' taurus SSHes to '''bobina''' and <code>open</code>s <code>Build kJams luna-pc.app</code> → luna-pc runs <code>build.bat</code>.
	* '''Win64 build:''' taurus SSHes to '''sugarbear''' and <code>open</code>s <code>Build kJams taurus-pc.app</code> → taurus-pc runs <code>build.bat</code>.		* '''Win64 build:''' taurus SSHes to '''sugarbear''' and <code>open</code>s <code>Build kJams taurus-pc.app</code> → taurus-pc runs <code>build.bat</code>.
	* '''USB code sign (from luna-pc or taurus Mac):''' SSH to '''sugarbear''' and <code>open</code> <code>code sign taurus-pc.app</code> or <code>code sign ~~path~~ taurus-pc.app</code>.		* '''USB code sign (from luna-pc or taurus Mac):''' SSH to '''sugarbear''' and <code>open</code> <code>code sign taurus-pc.app</code> or <code>code sign paths taurus-pc.app</code>.
	* '''Mac32:''' taurus SSHes to '''luna''' and <code>open</code>s <code>publish.command</code> / <code>rogue.command</code> (no WinAppHelper).		* '''Mac32:''' taurus SSHes to '''luna''' and <code>open</code>s <code>publish.command</code> / <code>rogue.command</code> (no WinAppHelper).
	* '''Mac64:''' taurus spawns a local Terminal worker with <code>KJAMS_WORKER=1</code>.		* '''Mac64:''' taurus spawns a local Terminal worker with <code>KJAMS_WORKER=1</code>.

Dave: rewrite: host/guest map, _scripts paths, luna-pc/taurus-pc names

2026-09-07T19:26:04Z

rewrite: host/guest map, _scripts paths, luna-pc/taurus-pc names

Show changes

Dave at 19:07, 7 September 2026

2026-09-07T19:07:50Z

← Older revision		Revision as of 19:07, 7 September 2026
Line 1:		Line 1:
	# go to your home folder		# go to your home folder
	# go to "Applications (Parallels)" -> "~~Windows 10~~ Applications"		# go to "Applications (Parallels)" -> "pandora-pc Applications"
	## to find the applications, to to Configure->Options->Applications, check the box "Show windows applications folder in dock", then you see the dock icon, right click reveal in finder)		## if you can not find the applications, to to Configure->Options->Applications, check the box "Show windows applications folder in dock", then you see the dock icon, right click reveal in finder)
	# copy "Command Prompt" to the desktop		# copy "Command Prompt" to the desktop
	# rename it "Build kJams"		# rename it "Build kJams"

Dave at 22:36, 12 December 2023

2023-12-12T22:36:25Z

← Older revision		Revision as of 22:36, 12 December 2023
Line 6:		Line 6:
	# right click->Show Package Contents		# right click->Show Package Contents
	# edit "/Contents/Info.plist"		# edit "/Contents/Info.plist"
	# change the "CFBundleGetInfoString" to end with:<br><pre>Z:\kJams\Development\xplat\proj\win\build.bat</pre>		# change the "CFBundleGetInfoString" to end with:<br><pre>Z:\depot\kJams\Development\xplat\proj\win\build.bat</pre>
	# change "CFBundleName" to:<br><pre>Build kJams</pre>		# change "CFBundleName" to:<br><pre>Build kJams</pre>
	# edit "/Contents/Resources/English.lproj/InfoPlist.strings"		# edit "/Contents/Resources/English.lproj/InfoPlist.strings"
	# change both "CFBundleName" and "CFBundleDisplayName" to:<br><pre>Build kJams</pre>		# change both "CFBundleName" and "CFBundleDisplayName" to:<br><pre>Build kJams</pre>
	# edit "/Contents/Resources/AppParams.pva"		# edit "/Contents/Resources/AppParams.pva"
	# change "App Path" to:<br><pre>Z:\kJams\Development\xplat\proj\win\build.bat</pre>		# change "App Path" to:<br><pre>Z:\depot\kJams\Development\xplat\proj\win\build.bat</pre>
	# Close out, put this new "app" into /xplat/proj/win/		# Close out, put this new "app" into /xplat/proj/win/

← Older revision		Revision as of 23:27, 7 September 2026
Line 78:		Line 78:
	== Sugarbear (taurus-pc, scripted) ==		== Sugarbear (taurus-pc, scripted) ==

	The three taurus-pc stubs are created by <code>create_sugarbear_winapphelpers.py</code>, which follows ~~this page's~~ recipe (~~including~~ the <code>~~CFBundleIdentifier~~</code> ~~step below~~). sugarbear's <code>/usr/bin/python3</code> is an Xcode license stub, so run the script on '''taurus''' (it SSHes to sugarbear only to copy the live Command Prompt). The <code>.sh</code> wrapper on sugarbear hops to taurus.		The three taurus-pc stubs are created by <code>create_sugarbear_winapphelpers.py</code>, which follows the recipe below (the same steps as [[Special:PermanentLink/13270\|December 2023]], with today's guest names and <code>_scripts</code> paths). sugarbear's <code>/usr/bin/python3</code> is an Xcode license stub, so run the script on '''taurus''' (it SSHes to sugarbear only to copy the live Command Prompt). The <code>.sh</code> wrapper on sugarbear hops to taurus.

	<pre>		<pre>
Line 87:		Line 87:
	That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.		That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.

	taurus-pc must be running. Do not run the script on pandora or bobina. After creating the stubs, copy them into the depot <code>xplat/proj/win/_scripts/</code> tree and '''submit''' — they belong in Perforce. <code>open</code> on sugarbear uses taurus's disk (sugarbear mounts it). Always <code>p4 sync</code> '''taurus''' after a pandora submit.		taurus-pc must be running. Do not run the script on pandora or bobina. After creating the stubs, copy them into the depot <code>xplat/proj/win\_scripts/</code> tree and '''submit''' — they belong in Perforce. <code>open</code> on sugarbear uses taurus's disk (sugarbear mounts it). Always <code>p4 sync</code> '''taurus''' after a pandora submit.

	Bobina is not scripted: Parallels there is version-locked for luna.		Bobina is not scripted: Parallels there is version-locked for luna.
Line 93:		Line 93:
	== Recipe (one stub, manual) ==		== Recipe (one stub, manual) ==

	Do ~~this~~ '''on bobina''' for <code>Build kJams luna-pc.app</code> (and anywhere you are not using the sugarbear script). The Windows guest must be running and logged into the GUI session you want the build to use~~. This is the original 2013 sequence; later edits dropped the identifier line~~.		This is the [[Special:PermanentLink/13270\|2023 sequence]] that produced working apps. Do it '''on bobina''' for <code>Build kJams luna-pc.app</code> (and anywhere you are not using the sugarbear script). The Windows guest must be running and logged into the GUI session you want the build to use.

	# On the hardware host, open the Parallels "Windows applications" folder for '''that''' guest (bobina: luna-pc Applications; sugarbear: taurus-pc Applications).		# On the hardware host, open the Parallels "Windows applications" folder for '''that''' guest (bobina: luna-pc Applications; sugarbear: taurus-pc Applications).
Line 101:		Line 101:
	# Right-click → Show Package Contents.		# Right-click → Show Package Contents.
	# Edit <code>Contents/Info.plist</code>:		# Edit <code>Contents/Info.plist</code>:
	#* <code>CFBundleGetInfoString</code> ~~must~~ '''~~end~~ with''' the <code>App Path</code> from the table (the <code>Z:\...\ _scripts\....bat</code> line).		#* Change <code>CFBundleGetInfoString</code> so it '''ends with''' the <code>App Path</code> from the table (the <code>Z:\...\ _scripts\....bat</code> line).
	#* <code>CFBundleName</code> = the exact bundle name without <code>.app</code>.		#* Change <code>CFBundleName</code> to the exact bundle name without <code>.app</code>.
	#* <code>CFBundleIdentifier</code>: insert the stub name immediately after <code>com.parallels.winapp.</code> (hyphenate spaces; a reverse-DNS id cannot contain spaces). The 2013 page said: add <code>.Build kJams</code> just after <code>.winapp</code>. Example: <code>com.parallels.winapp.b7210c99…</code> becomes <code>com.parallels.winapp.Build-kJams-luna-pc.b7210c99…</code>. '''Do not leave the live Command Prompt identifier''' — Launch Services / Parallels will reuse that helper and ignore this stub's <code>APP Path</code>. Also set the identifier in <code>English.lproj/InfoPlist.strings</code> if that file has one.
	# Edit <code>Contents/Resources/English.lproj/InfoPlist.strings</code>: set both <code>CFBundleName</code> and <code>CFBundleDisplayName</code> to that same name.		# Edit <code>Contents/Resources/English.lproj/InfoPlist.strings</code>: set both <code>CFBundleName</code> and <code>CFBundleDisplayName</code> to that same name.
	# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path~~. Confirm <code>VM Name</code> is luna-pc or taurus-pc as appropriate~~.		# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path.
	# ~~Move~~ the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).		# Close out, put the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).
	# You only need the manual copy once on bobina (<code>Build kJams luna-pc.app</code>). sugarbear's three stubs come from the Python script above.		# You only need the manual copy once on bobina (<code>Build kJams luna-pc.app</code>). sugarbear's three stubs come from the Python script above.

			Do '''not''' edit <code>CFBundleIdentifier</code>. Leave it as Parallels wrote it on Command Prompt.

	== Hop (what taurus actually does) ==		== Hop (what taurus actually does) ==

← Older revision		Revision as of 23:04, 7 September 2026
Line 78:		Line 78:
	== Sugarbear (taurus-pc, scripted) ==		== Sugarbear (taurus-pc, scripted) ==

	The three taurus-pc stubs are created on '''~~sugarbear~~''' ~~by:~~		The three taurus-pc stubs are created by <code>create_sugarbear_winapphelpers.py</code>, which follows this page's recipe (including the <code>CFBundleIdentifier</code> step below). sugarbear's <code>/usr/bin/python3</code> is an Xcode license stub, so run the script on '''taurus''' (it SSHes to sugarbear only to copy the live Command Prompt). The <code>.sh</code> wrapper on sugarbear hops to taurus.

	<pre>		<pre>
	~~/bin/bash~~ /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.sh --dry-run		python3 /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.py --dry-run
	~~/bin/bash~~ /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.sh		python3 /Volumes/Developer/depot/kJams/Development/xplat/python/create_sugarbear_winapphelpers.py
	</pre>		</pre>

	That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.		That copies the live Parallels '''Command Prompt''' app for taurus-pc (Helper Version 27 as of 2026-09) and points <code>APP Path</code> at the bats in the table. Precise recipe: depot <code>xplat/python/create_sugarbear_winapphelpers.md</code>.

	taurus-pc must be running. Do not run the script on ~~taurus,~~ pandora, or bobina. After creating the stubs, copy them into the depot <code>xplat/proj/win/_scripts/</code> tree and '''submit''' — they belong in Perforce. <code>open</code> on sugarbear ~~still~~ uses ~~that host~~'s ~~copy of the same path~~. Always <code>p4 sync</code> '''taurus''' after submit ~~(self-contained workspace, not pandora's disk)~~.		taurus-pc must be running. Do not run the script on pandora or bobina. After creating the stubs, copy them into the depot <code>xplat/proj/win/_scripts/</code> tree and '''submit''' — they belong in Perforce. <code>open</code> on sugarbear uses taurus's disk (sugarbear mounts it). Always <code>p4 sync</code> '''taurus''' after a pandora submit.

	Bobina is not scripted: Parallels there is version-locked for luna.		Bobina is not scripted: Parallels there is version-locked for luna.

	== Recipe (~~bobina / luna-pc,~~ one stub, manual) ==		== Recipe (one stub, manual) ==

	Do this '''on bobina''' for <code>Build kJams luna-pc.app</code>. ~~luna-pc~~ must be running and logged into the GUI session you want the build to use.		Do this '''on bobina''' for <code>Build kJams luna-pc.app</code> (and anywhere you are not using the sugarbear script). The Windows guest must be running and logged into the GUI session you want the build to use. This is the original 2013 sequence; later edits dropped the identifier line.

	# On ~~bobina~~, open the Parallels "Windows applications" folder for '''luna-pc~~'''~~.		# On the hardware host, open the Parallels "Windows applications" folder for '''that''' guest (bobina: luna-pc Applications; sugarbear: taurus-pc Applications).
	## If you cannot find it: Parallels → Configure → Options → Applications → enable "Show Windows applications folder in Dock". Dock icon → Reveal in Finder.		## If you cannot find it: Parallels → Configure → Options → Applications → enable "Show Windows applications folder in Dock". Dock icon → Reveal in Finder.
	# Copy '''Command Prompt''' to the Desktop.		# Copy '''Command Prompt''' to the Desktop.
Line 103:		Line 103:
	#* <code>CFBundleGetInfoString</code> must '''end with''' the <code>App Path</code> from the table (the <code>Z:\...\ _scripts\....bat</code> line).		#* <code>CFBundleGetInfoString</code> must '''end with''' the <code>App Path</code> from the table (the <code>Z:\...\ _scripts\....bat</code> line).
	#* <code>CFBundleName</code> = the exact bundle name without <code>.app</code>.		#* <code>CFBundleName</code> = the exact bundle name without <code>.app</code>.
			#* <code>CFBundleIdentifier</code>: insert the stub name immediately after <code>com.parallels.winapp.</code> (hyphenate spaces; a reverse-DNS id cannot contain spaces). The 2013 page said: add <code>.Build kJams</code> just after <code>.winapp</code>. Example: <code>com.parallels.winapp.b7210c99…</code> becomes <code>com.parallels.winapp.Build-kJams-luna-pc.b7210c99…</code>. '''Do not leave the live Command Prompt identifier''' — Launch Services / Parallels will reuse that helper and ignore this stub's <code>APP Path</code>. Also set the identifier in <code>English.lproj/InfoPlist.strings</code> if that file has one.
	# Edit <code>Contents/Resources/English.lproj/InfoPlist.strings</code>: set both <code>CFBundleName</code> and <code>CFBundleDisplayName</code> to that same name.		# Edit <code>Contents/Resources/English.lproj/InfoPlist.strings</code>: set both <code>CFBundleName</code> and <code>CFBundleDisplayName</code> to that same name.
	# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path. Confirm <code>VM Name</code> is luna-pc or taurus-pc as appropriate.		# Edit <code>Contents/Resources/AppParams.pva</code>: set <code>APP Path</code> (or <code>App Path</code>) to the same <code>Z:\...</code> bat path. Confirm <code>VM Name</code> is luna-pc or taurus-pc as appropriate.
	# Move the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).		# Move the finished <code>.app</code> into <code>/Volumes/Developer/depot/kJams/Development/xplat/proj/win/_scripts/</code> (same path on the host via the Developer share).
	# You only need ~~this~~ once on bobina (<code>Build kJams luna-pc.app</code>). sugarbear's three stubs come from the script above~~, not from this copy-Command-Prompt list~~.		# You only need the manual copy once on bobina (<code>Build kJams luna-pc.app</code>). sugarbear's three stubs come from the Python script above.

	== Hop (what taurus actually does) ==		== Hop (what taurus actually does) ==
Line 119:		Line 120:

	* Depot docs: <code>Development/documentation/01_Infrastructure_Overview.md</code>		* Depot docs: <code>Development/documentation/01_Infrastructure_Overview.md</code>
			* <code>Development/xplat/python/create_sugarbear_winapphelpers.py</code>
	* <code>Development/xplat/python/create_sugarbear_winapphelpers.md</code>		* <code>Development/xplat/python/create_sugarbear_winapphelpers.md</code>
	* <code>CF/python/xplat.py</code> — <code>guest_to_host()</code>, <code>get_win_build_apphelper_name()</code>		* <code>CF/python/xplat.py</code> — <code>guest_to_host()</code>, <code>get_win_build_apphelper_name()</code>