Please see the attached patch that solves the problem with warnings. I am wondering why there is a need to hardcode installation paths as they usually are not only OS dependent but also architecture dependent . And cmake on windows handle them correctly by default...
On Sun, 4 Oct 2020 at 03:54, Greg Hellings <greg.helli...@gmail.com> wrote: > Sword doesn't really support building on Windows other than with the > Borland C++ files that Troy maintains. CMake can easily be used to > cross-compile from Linux. > > If you would like to provide fixes to it so that it also builds directly > from Windows with CMake, you're welcome to send those to the list or to me > directly. > > --Greg > > On Sat, Oct 3, 2020 at 4:09 AM ZdPo Ster <zdpos...@gmail.com> wrote: > >> cmake 3.18.2 (on windows) reports: >> >> CMake Warning (dev) at cmake/options.cmake:21 (set): >> Syntax error in cmake code at >> >> F:/Project-Personal/clang_shared/sword-1.9.0RC3/cmake/options.cmake:21 >> >> when parsing string >> >> Directory into which to install architecture-dependent files. >> Defaults to C:\Program Files (x86)\libsword\. >> >> Invalid escape sequence \P >> >> Policy CMP0010 is not set: Bad variable reference syntax is an error. >> Run >> "cmake --help-policy CMP0010" for policy details. Use the cmake_policy >> command to set the policy and suppress this warning. >> Call Stack (most recent call first): >> cmake/options.cmake:35 (_SET_FANCY) >> CMakeLists.txt:31 (INCLUDE) >> This warning is for project developers. >> >> cmake & VS build is ok. >> But when I tried to build sword with cmake and clang (which is able to >> create libraries compatible with VS or gcc) via ninja I got error message: >> >> failed with: >> ninja: error: build.ninja:2837: multiple rules generate sword.lib >> >> IMO these are not showstoppers, but it would be nice to solve them in the >> final release... >> >> Zdenko >> >> On Fri, 2 Oct 2020 at 22:00, Karl Kleinpaste <k...@kleinpaste.org> wrote: >> >>> On 10/2/20 9:42 AM, Troy A. Griffitts wrote: >>> >>> Please give it a try and let me know if you have any issues >>> >>> No issue building, and building Xiphos with it. >>> >>> But important question: Does this release take care of the UTF-16 >>> problem? I know that was being discussed some months back. That is, will we >>> be able to dispose of the decade-old patch for Win32 Sword that keeps >>> Xiphos sane in the face of NTFS and đíàçŕïẗ́iċąłṡ? >>> _______________________________________________ >>> sword-devel mailing list: sword-devel@crosswire.org >>> http://crosswire.org/mailman/listinfo/sword-devel >>> Instructions to unsubscribe/change your settings at above page >> >> _______________________________________________ >> sword-devel mailing list: sword-devel@crosswire.org >> http://crosswire.org/mailman/listinfo/sword-devel >> Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page
cmake.patch
Description: Binary data
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
