On 6/28/18, 4:54 AM, "Ryan Schmidt" <[email protected]> wrote: On Jun 27, 2018, at 13:47, Langer, Stephen A. (Fed) wrote: > It requires knowing the installation prefix during the distutils build stage, which certainly can be done, but I don't think it's standard in the distutils world. At least, the prefix isn't accessible to the build_ext command in the python 2.7 distutils. The easiest solution would be for the distutils build_ext command to copy the value from the distutils install command, but that requires them to be run together in the MacPorts build phase, which breaks the MacPorts model. It could be set twice, once as a build argument and once as an install argument, which is ugly but might work. I'll try it. Yes there are many ports that supply the same arguments and/or environment variables at both build and destroot time. It's a simple one-liner in a Portfile to copy all the args, for example. It's easy to do in the Portfile, but it's suboptimal to force users who can barely read the instructions to do it when installing manually. In any case, thanks to all of your suggestions, I can now build and install using the Portfile. I can create an mpkg and install from it. However, the contents of the mpkg are incorrect. There are missing symbols in libgio-2.0.dylib, which is installed by the glib2 port, so I suspect it has something to do with with https://trac.macports.org/ticket/54981. I installed glib2 with +x11 and installed everything else with +quartz, which is the only way to get gtk2 working on quartz. Would mpkg have somehow pulled in the +quartz version? If my port requires a particular version, do I have to do something to enforce it when packaging the port? The correct libgio-2.0.dylb defines _g_desktop_app_info_get_type. The one in the mpkg defines _g_osx_app_info_get_type instead. Googling "glib osx_app_info" leads to a page with Ryan's name on it… I've attached my portfile, in case it helps. -- Steve
Portfile
Description: Portfile
