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 CrossWire site will have > the latest version from SVN. > > Just a "nice to have" rather than an absolute necessity.
I've looked more closely at this issue and it turns out that the utilities you name are specifically listed in the SWORD build code as being programs which ought to be compiled but which ought not to be installed. Therefore I am not installing them when I build the SWORD package Xiphos builds against and they are not being packaged up at all. I'm not sure why these in particular in in the utilities/ directory, are built, but are disabled for install. I crafted the CMake build system very closely on the autotools system where they were already listed as noinst_PROGRAMS and where they remain. If someone else would like to answer why these are not distributed as SWORD binaries then we can have an answer to this riddle. --Greg > > David > > -- > View this message in context: > http://sword-dev.350566.n4.nabble.com/Sword-utils-not-shipped-with-Xiphos-for-Windows-tp4435162p4435220.html > Sent from the SWORD Dev mailing list archive at Nabble.com. > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page _______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
