Iāve spent a bit of time trying to get the build working on 64-bit Windows 10 and Windows 11 without succerss yet. In addition to trying with the 7.3.3 source tarball, Iāve tried using a github clone as well as a bk repo Harlan Stenn had squirelled away apparently dating to a time when 7.3.3 sources were available from bkbits.net.
One very minor problem was that on a 64-bit Windows 10 system, the 8.3 path to the installed BitKeeper 7.3.2 was āc:\progra~2\bitkee~1ā rather than progra~1.
If the bitkeeper.com Win7 build VM is still stored somewhere, it might be a bunch easier if the 7.3.2 working \build tree from that box were available.
I tried saving several build log by adding ā| tee build_p.logā but sadly those logs I now see contain only āsh mkconf.sh > conf.mk || { rm -f conf.mk; false; }ā.
I do have these notes I kept on one attempt:
bk build steps on windows 10 x64
verified bk installed (/build/bk-7.3.2-wscott/src)
verified git installed (git version 2.39.1.windows.1)
from an elevated cmd:
mkdir c:\build
cd /d c:\build
git clone httpsā¦//github.com/bitkeeper-scm/bitkeeper.git dev
from an elevated VS 2022 x64_x86 Cross Tools Command Prompt:
echo set path=%path% >p.bat
rem edited p.bat to remove the three git directories to ensure no mingw-like tools on path
p.bat
cd /d c:\build
rem re: build instructions said to use bk tar zxf ā¦ but:
rem c:\build>bk tar zxf win32-buildenv.tgz
rem bk: ātarā is not a BitKeeper command.
rem however win10 tar is fine:
tar zxf win32-buildenv.tgz
tar zxf win32tools.tgz
cd dev
buildenv
I answered no to removing buildenv.
Then from bash:
BUILD src $ ./build p | tee ā¦/build_p.log
That reported errors and failed in case those were not significant I proceeded
BUILD src $ ./build image | tee ā¦/build_image.log
but it errored out very similarly. Both failures seem to be because I wasnāt building in a bk repo.
However:
c:\build>dev\src\bk version
BitKeeper version is NOFILE for x86-win32
Built by: NOFILE in /build/dev/src
Built on: Mon Jan 30 2023 11:05:56 Eastern Standard Time (123 seconds ago)
Running on: x86-win32,Windows_10_Enterprise-64
Latest version: bk-7.3.3 (released 5 years ago)
butā¦
c:\build>dir dev\src*.exe
Volume in drive C is OS
Volume Serial Number is B4FE-DB48
Directory of c:\build\dev\src
01/30/2023 11:05 AM 7,676,383 bk.exe
01/30/2023 11:03 AM 2,611,678 bkg.exe
01/30/2023 11:03 AM 28,160 svcmgr.exe
3 File(s) 10,316,221 bytes
0 Dir(s) 611,159,904,256 bytes free
c:\build>cd dev\src
c:\build\dev\src>bk helptool
Cannot find the graphical interpreter.
c:\build\dev\src>set path=c:\build\dev\src;%path%
c:\build\dev\src>bk helptool
Cannot find the graphical interpreter.
c:\build\dev\src>bk clone \ntp\stable\tracking \ntp\stable\tracking2
Clone file:///ntp/stable/tracking
ā file:///ntp/stable/tracking2
clone 100% |==============================| OK
c:\build\dev\src>bk repocheck \ntp\stable\tracking2
Cannot find the L interpreter.
c:\build\dev\src>
Thanks for your heroic volunteer efforts keeping the bk community going. I will make some more attempts to get bk building on Windows so I can try to restore the SSH support that appears to have been intentionally disabled for Windows bk.
