Opened 10 years ago
Closed 6 years ago
#43844 closed update (fixed)
fontforge: upgrade to latest version
Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | cooljeanius (Eric Gallager), iapain@…, ryandesign (Ryan Carsten Schmidt), matt-macports@…, herrbischoff (Marcel Bischoff) | |
Port: | fontforge |
Description
I'm looking for volunteers to bring FontForge up to date.
Change History (13)
comment:1 Changed 10 years ago by cooljeanius (Eric Gallager)
Cc: | egall@… added |
---|
comment:2 Changed 10 years ago by mojca (Mojca Miklavec)
Cc: | iapain@… added |
---|
comment:3 Changed 10 years ago by dbevans (David B. Evans)
Cc: | ryandesign@… added |
---|
Current version is 20141230 (v2.1).
comment:6 Changed 8 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | marcel@… added |
---|---|
Summary: | fontforge: upgrade to version 2.0 → fontforge: upgrade to latest version |
Has duplicate #51821. Current version available upstream is 20160404.
comment:7 Changed 7 years ago by tessus (Helmut K. C. Tessarek)
Please have a look at https://github.com/tessus/macports-ports/commit/dc6013224ca91ff937c62d0f887749a324872aca
fontforge 20170731
The Portfile can be improved so that PYTHON_CFLAGS
and PYTHON_LIBS
are not hardcoded.
They should rather be set as follows:
PYTHON_CFLAGS="`${PYTHON}-config --cflags`" PYTHON_LIBS="`${PYTHON}-config --ldflags`"
I just do not know how to do that in the Portfile
.
I've also noticed that sudo port install -vst fontforge [+python27]
abends in the configure
phase for some obscure reason.
However, it compiles and installs perfectly without -t
.
Please note that the OSX GUI app compiles correctly, but is unusable for no apparent reason. I tried to get some info about this issue upstream, but they couldn't help. I believe they don't care about the OSX GUI app anymore. This is the reason why I removed the configure options --x-includes=${prefix}/include --x-libraries=${prefix}/lib
and replaced them with --without-x
.
comment:8 follow-up: 10 Changed 7 years ago by raimue (Rainer Müller)
Do not hardcode PYTHON_CFLAGS
and PYTHON_LIBS
at all. The build system will figure it out itself based on the python binary you pass as PYTHON
. However, it needs the configuration file for pkg-config. Because python is packaged strangely, this is not in the normal search path (I consider it a bug in the python ports).
You should only need this:
configure.env-append PYTHON=${prefix}/bin/python2.7 \ PKG_CONFIG_PATH="${frameworks_dir}/Python.framework/Versions/2.7/lib/pkgconfig"
A application using X11 does not really sound specific to macOS. Have you tried launching it from command line instead of with the .app
bundle the port puts together? Probably only the latter has a problem.
comment:9 Changed 7 years ago by pmetzger (Perry E. Metzger)
Helmut, after doing raimue's suggested fixes, please make a pull request to the main repo? I promise we will handle it quickly.
comment:10 Changed 7 years ago by jmroot (Joshua Root)
Replying to raimue:
configure.env-append PYTHON=${prefix}/bin/python2.7 \ PKG_CONFIG_PATH="${frameworks_dir}/Python.framework/Versions/2.7/lib/pkgconfig"
Note that there are specific options for both of these, configure.python
and configure.pkg_config_path
.
comment:11 Changed 7 years ago by mojca (Mojca Miklavec)
comment:12 Changed 6 years ago by tessus (Helmut K. C. Tessarek)
comment:13 Changed 6 years ago by mf2k (Frank Schima)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Cc Me!