Nine executables normally found in Sword utilities are not included in the
Xiphos bin folder.
See diff file pasted below:
diff B xiphos.exe.log utils.exe.log
0a1
addgb.exe
1a3,4
addvs.exe
cipherraw.exe
3,5c6,7
gdb.exe
gspawn-win32-helper-console.exe
gspawn-win32-helper.exe
---
Greg already explained (under the other thread):
Because I had $ ls -l /usr/i686-w64-mingw32/sys-root/mingw/bin/ | wc -l286
files to look through when creating the Xiphos package and I had to
identify at a glance which ones were relevant.
Also because the public had access to several betas of
On Thu, Mar 1, 2012 at 8:41 AM, David Haslam dfh...@googlemail.com wrote:
Nine executables normally found in Sword utilities are not included in the
Xiphos bin folder.
See diff file pasted below:
diff B xiphos.exe.log utils.exe.log
0a1
addgb.exe
1a3,4
addvs.exe
cipherraw.exe
3,5c6,7
On Thu, Mar 1, 2012 at 9:03 AM, David Haslam dfh...@googlemail.com wrote:
Thanks Greg,
Can you add the really useful ones, like emptyvss, to the next release?
This would ensure that anyone who install a Xiphos version that happens to
be more recent than the compiled utilities on the
On 1.3.2012 15:41, David Haslam wrote:
Nine executables normally found in Sword utilities are not included in the
Xiphos bin folder.
Couldn't the specialized utilities intended for developers rather than
end-users be provided separately? E.g., in the page you mentioned in
other thread
On Thu, Mar 1, 2012 at 12:04 PM, Matej Cepl mc...@redhat.com wrote:
On 1.3.2012 15:41, David Haslam wrote:
Nine executables normally found in Sword utilities are not included in the
Xiphos bin folder.
Couldn't the specialized utilities intended for developers rather than
end-users be
