Differences From:
File
win32.txt
part of check-in
[5890c67d86]
- Added win32 build notes
by
jnc on
2007-09-21 22:07:35.
[view]
To:
File
win32.txt
part of check-in
[c7278fd013]
- Win32 port now functional except network operations. This commit was done on windows :-). See win32.txt for status of all commands. No networking commands are functional yet. All path operations are now functioning.
by
jnc on
2007-09-22 06:47:11.
[view]
@@ -12,4 +12,88 @@
Download/compile/install tclsh (configure --prefix=/) (for tests)
All commands were issued in the MSYS shell, not a cmd.exe
+
+
+Outstanding Issues:
+----------------------------------------------------------------------
+
+* server is totally non-functional - #if/#end'd out of the code
+* all path operations are defunct
+* remote network operations are reporting: can't resolve host name: xyz
+
+ Winsock must be initialized before using:
+
+ WSADATA info;
+ if (WSAStartup(MAKEWORD(1,1), &info) != 0){
+ fossil_panic("can't initialize winsock");
+ }
+
+
+
+Commands status:
+----------------------------------------------------------------------
+
+add OK
+cgi Not tested
+changes OK
+checkout BAD #1
+clean OK
+clone Local Only #2
+close OK
+commit OK (not tested with gpg signing yet)
+config OK
+deconstruct OK
+del OK
+descendents OK
+diff OK
+extra OK
+help OK
+http Not Tested
+info OK
+leaves OK
+ls OK
+merge OK
+new OK
+open OK
+pull BAD #2
+push BAD #2
+rebuild OK (didn't have a corrupt file to try on though)
+redo BAD #3
+rm OK
+server BAD #2,#4
+status OK
+sync BAD #2
+timeline OK
+tkdiff OK
+undo OK
+update OK
+user capabilities OK
+user default OK
+user list OK
+user new OK
+user password OK
+
+#1 Have a repo where I removed a file. I did a fossil checkout 123abc,
+ which is the last version that had the file. The file does not
+ appear. fossil checkout --force 123abc does things, but still the
+ file does not appear.
+
+ Make a new dir, fossil open ../repo.fsl && fossil checkout 123abc and
+ the file appears.
+
+ Is that normal operation?
+
+#2 No socket operations are functioning yet
+
+#3 In test1/ I edited a file, test2/ I updated, type file.txt changes
+ were there. I then did fossil undo file.txt. The changes were gone
+ and fossil status said I had edited file.txt. A fossil redo did not
+ print anything to the screen and the changes for file.txt are not
+ in the file. fossil status still reports that the file was edited.
+ There was no commit/update or any other command inbetween these
+ actions.
+
+#4 There were various difficulties in this function beyond simple socket
+ problems. The major one being fork. This will probably be the last
+ command to be functional in fossil on windows.