Oh, it is possible to modify binary, after build, to embed specific library
locations using
install_name_tool . see
http://www.unix.com/man-page/osx/1/install_name_tool/
On Sat, 26/3/16, Hin-Tak Leung wrote:
The
The library dependence is likely dynamic... you could examine which copy of the
library
it is trying to load by:
otool -L
To some extent, you can override it with:
export DYLD_LIBRARY_PATH=/opt/X11/lib
before you run the binary, but this is generally frown upon, as other things
may break.
Oh, I see now that
/usr/X11 and /usr/X11R6 are symlinked (rightly) to /opt/X11
So there's a bunch of things like libfreetype, libcairo etc. in /opt/X11
(aka /usr/X11) and, separately, in /usr/local
But this is not different from what I had a month ago.
On Sat, Mar 26, 2016 at 5:52 PM, Adam
In xterm, there is extra
X11_PREFS_DOMAIN=org.macosforge.xquartz.X11
XTERM_LOCALE=en_US.UTF-8
XTERM_SHELL=/bin/bash
XTERM_VERSION=XTerm(322)
but otherwise the env vars are the same.
A.
On Sat, Mar 26, 2016 at 4:15 PM, suzuki toshiya
wrote:
> There is no difference
Nikolaus,
I tried both
On Sat, Mar 26, 2016 at 4:20 PM, Nikolaus Waxweiler
wrote:
> Out of curiosity, are you starting the tools from the build directory or
> after you `make install`?
>
> ___
> Freetype-devel mailing list
>
Ah, yes. I do indeed have cairo, mupdf installed via brew in /usr/local,
freetype is also there (built myself). mupdf comes from the "x11" group of
things installed by brew. When I try to launch mupdf-x11, I get
error: cannot open display
uncaught exception: cannot open display
Then I have
do you have multiple versions of some libraries (possibly freetype) under
both /opt/X11/lib and /usr/local/lib ? Possibly also cairo, etc?
The X server should be launched on demand by launchd, but it does depend
on you trying to access those versions of libraries under /opt/X11, and not
other
Out of curiosity, are you starting the tools from the build directory or
after you `make install`?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
There is no difference in environment variables
between the shell in xterm and that in Terminal.app?
Adam Twardoch (Lists) wrote:
Well, I guess the problem may be on a different level. When I launch
`ftmulti` from the XQuartz-provided terminal (xterm), then it launches
correctly (with the
Well, I guess the problem may be on a different level. When I launch
`ftmulti` from the XQuartz-provided terminal (xterm), then it launches
correctly (with the GUI). But if I launch it from within the regular "text"
Terminal or iTerm apps, then I get the error. Same with `ftview` etc.
cannot open
Dear Adam,
Do you mean that other X11 programs (e.g. xterm) could
be started correctly, but ft2demos could not be?
I will try to find some access to the recent Mac OS X...
Regards,
mpsuzuki
Adam Twardoch (Lists) wrote:
> I once somehow had managed to build a version of ft2demos tools which
> macro AF_LATIN_BLUE_MAX in file aflatin2.c is not defined.
Thanks for the report. Note, however, that the file `aflatin2.c'
doesn't work or compile at all – I let it in the source code bundle
until I find time to analyze the algorithm, then it will probably be
removed.
Werner
I once somehow had managed to build a version of ft2demos tools which
worked with the OS X X11 (XQuartz) server.
But now, with the standard "autogen.sh then make" of current git FreeType
plus the "make" of current git ft2demos, the tools build but when trying to
use them, I get:
ftmulti 72
13 matches
Mail list logo