X-Git-Url: https://feistymeow.org/gitweb/?a=blobdiff_plain;f=doc%2Fbinaries_note.txt;h=d56dfe39fc13d8017bf2344e808d370a50d6d492;hb=43d671a278a6f7dc0d831541d0992bc00eb23ee8;hp=a4b7849df4cf0749876c913e730078a68f8d5c07;hpb=e5f4d647d5b8d83155fc4b142626fc204cc2c15b;p=feisty_meow.git diff --git a/doc/binaries_note.txt b/doc/binaries_note.txt index a4b7849d..d56dfe39 100644 --- a/doc/binaries_note.txt +++ b/doc/binaries_note.txt @@ -1,27 +1,12 @@ -There are a few pre-built binaries included with this code distribution. -They originate from a few different sources. Feel free to not trust them. - -These apps are external to the feisty meow build... - -production/msys hierarchy: - This is copied directly from the msys project of MingW. - It has had zip.exe, unzip.exe and short_path.exe added to it: - - unzip.exe & zip.exe: - The zip and unzip tools are from the info-zip project. They are somewhat - antiquated but still work great on the various 32-bit windows platforms. - These utilities are self-identified as: "Zip 2.3 (November 29th 1999)" - To get a more recent version of the zip utilities or build them yourself, - they can be found at the site: http://www.info-zip.org/ - - short_path.exe: - This tool is built by the code bootstrapping process (that is, by - scripts/generator/bootstrap_build.sh), but unfortunately it is - desperately needed for windows builds to work nicely with clam and - bash. If you don't have it, and your visual studio installation path - has spaces in it, then you may have trouble bootstrapping. You can - manually change your VC root variable to a short path version, as - reported by dir /x). This tool can be replaced by any newer working - version created by a bootstrap build. +There is one pre-built binary included with this code distribution +in the production/win32_helper folder. Feel free to not trust it. + +short_path.exe: + This tool is built by the feisty meow application bootstrapping process + (that is, by scripts/generator/produce_feisty_meow.sh), but unfortunately it is + needed *by* that process when your visual studio installation path has + spaces in it. To fix this chicken & egg problem, you can manually change + your VC root variable (e.g. VS100COMNTOOLS) to the short path version (as + reported using "dir /x").