[sword-devel] Build Failure in path with spaces

[David Haslam]

Lateral thoughts ....

How might a build work or fail if the SWORD path contains any non-ASCII characters?

This is certainly conceivable for Windows users whose locale is not English.
I cannot speak for Linux users.

Best regards,

David

Sent from ProtonMail Mobile

On Wed, Apr 8, 2020 at 09:17, Greg Hellings <greg.hellings at gmail.com> wrote:

> So there's a two-fold failure during compile when handling paths with spaces.
>
> The first is that the build fails when the code is in a path that has spaces in it. This is because instances of "-I${some_foo}/include" in autotools are not wrapped with quotation marks.
>
> The second is when you invoke: ./configure --prefix="/some/path with a space/in/it" --sysconfdir="/som/other/path with spaces". This is because SWICU_DATA and GLOBCONFPATH are not properly escaped for that situation, either.
>
> An additional frustration, since I was in the autotools already to fix this (the path on the CI server has spaces in it, because I absentmindedly created the job with spaces in it) is that I can't finish a compile with autotools out of stream (I like to do my builds in a subdir of the main source dir so that things build artifacts and generated objects aren't being intermingled with the code).
>
> So I've attached a patch that fixes all of these problems.
>
> --Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.crosswire.org/pipermail/sword-devel/attachments/20200413/e47646d8/attachment.html>