Re: [Tuxpaint-devel] Per-locale default font

[Mark K. <mar...@gm...>]

Would this work?

diff --git a/Makefile b/Makefile
index 331604b1..f5b1497f 100644
--- a/Makefile
+++ b/Makefile
@@ -886,7 +886,7 @@ echo-thumb-starters:
        @echo "# Don't let ImageMagick use Inkscape; use rsvgconvert
instead" > ./inkscape
        @echo "exit 1" >> ./inkscape
        @chmod 755 ./inkscape
-       @(eval export PATH="$(shell pwd)":"$(PATH)")
+       $(eval export PATH=$(shell pwd):$(PATH))

 # Create thumbnails for starters
 .PHONY: thumb-starters


On Fri, Jun 16, 2023 at 2:00 PM Bill Kendrick <nb...@so...> wrote:

> On Fri, Jun 16, 2023 at 06:01:02PM +0900, Shin-ichi TOYAMA wrote:
> > Hi!
> >
> > As a workaround on my build environment, I've purged paths containing
> > spaces and parentheses from the "$PATH" and added paths of symbolic
> > links from /usr/local/* to actual directories.
> >
> > It looks O.K. so far.
>
> Thanks.
>
> I was actually just thinking out loud in an email to Tim, suggesting
> perhaps
> we can just create our own tiny shell script that gets invoked
> (call it, say, `./convert-wrapper.sh`) rather than the `convert` in $PATH,
> so we can have full control over how it works...
>
> ...either by doing a similar "inkscape => exit 1", to convince
> ImageMagick's
> `convert` to fall back to using `rsvgconvert`...
>
> ...or by simply looking at the filename extension of what's being fed to
> the script by Makefile (we control these files, they are the ones that
> ship with the source .tar.gz), and either run ImageMagick's `convert` if
> it's a PNG file, or `rsvgconvert` _directly_ if it's an SVG file.
>
> Another idea I mulled over was somehow overriding ImageMagick's
> delegate for SVG, or adding a new delegate and using some kind of prefix,
> but (1) this is getting way over complicated (compared to a tiny .sh
> script),
> and (2) I'm not [very quickly] figuring out how to do that, or whether it's
> even possible.  (Apparently, ImageMagick can look at a user's personal
> delegates file, but we'd want it to be even _more_ "local" than that,
> a file right inside the `tuxpaint` source tree somewhere.)
> (Basically, after a minute of Googling, I gave up trying to find out. ;) )
>
> -bill!
>
> >
> > Thanks.
> >
> > On Thu, 15 Jun 2023 23:03:20 +0900, Shin-ichi TOYAMA wrote:
> > >On Tue, 13 Jun 2023 22:20:40 -0700, Bill Kendrick wrote:
> > >>> By the way, I had to revert the commit
> "cf94635713b9dc7977af131a6b3ec89cc872d0e1"
> > >>> to build Tux Paint on Windows from current git repo because of the
> error as follows.
> > >>
> > >>Ah, I wonder if adding quotes would help.  (I get the feeling the "("
> in question
> > >>might be from the "(x86)"?)
> > >
> > >Sure, I confirmed that the parentheses and whitespaces in the PATH,
> which are common
> > >on Windows, are the evil.
> > >
> > >>Does
> https://sourceforge.net/p/tuxpaint/tuxpaint/ci/7febf719d02e9c78d4554d2388d793726e19b0af/
> > >>help?
> > >
> > >Unfortunately it doesn't.
> > >
> > >I confirmed that not using 'eval' causes no error after trial and error
> aproach, but
> > >I'm not sure if it is a right way or not.
> > >
> > >----------------------------------------------------
> > >-       @(eval export PATH="$(shell pwd)":"$(PATH)")
> > >+       @export PATH="$(shell pwd)":"$(PATH)"
> > >----------------------------------------------------
> > >
> > >
> > >_______________________________________________
> > >Tuxpaint-devel mailing list
> > >Tux...@li...
> > >https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
> >
> >
> > --
> > Shin-ichi TOYAMA <dol...@wm...>
> >
> >
> > _______________________________________________
> > Tuxpaint-devel mailing list
> > Tux...@li...
> > https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>
> --
> -bill!
> Sent from my computer
>
>
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
>