Re: Missing files in distribution
Paul Wessel <[email protected]>
| Newsgroups | gmane.comp.printing.ghostscript.devel |
|---|---|
| Message-ID | <[email protected]> |
Thank Chris, I am happily served by the shared library. I just wanted to try following the instructions for framework building. Perhaps just removing that text from instructions would be good enough. Cheers, Paul Sent from my iPad > On Nov 14, 2015, at 11:17 PM, Chris Liddell <[email protected]> wrote: > >> On 15/11/15 09:11, Chris Liddell wrote: >>> On 15/11/15 03:34, Paul Wessel wrote: >>> I am interested in building the OS X Framework for ghostscript under El Capitan. However, your instructions of use base/macosx.mak as the top-level makefile and run “make framework” fails because key files are missing: >>> >>> Makefile:425: base/devs.mak: No such file or directory >>> Makefile:426: base/contrib.mak: No such file or directory >>> … >>> Makefile:430: base/macos-fw.mak: No such file or directory >>> make: *** No rule to make target `base/macos-fw.mak'. Stop. >>> >>> Clearly, the macos-fw.mak would be very relevant here. However, I am able to build the shared library. Can the framework no longer be built? >> >> The framework build has not worked in a long time (>5 years, AFAIK). >> We've only had queries about the shared library since I took over >> maintaining the builds, so that's where why time has been devoted. >> >> TBH, I don't have any idea of what would be involved in getting >> framework support up and building again. >> >> FWIW, there aren't any files missing in the distro, the problem is that >> on Unix-like systems we *only* support the configure based build, so >> using base/macosx.mak as the top level makefile will not include any of >> the settings that come from the configure script. >> >> Also, there has been considerable reorganisation of the directory >> structures, not all of which are reflected in the likes of base/macosx.mak. >> >> If you have a genuine reason why you cannot use the shared library, and >> *must* have the framework, I can look into what would be required to get >> it working again - but I would have no solid way of testing it, so..... > > In fact, the macos-fw.mak file *is* missing from recent recent releases > (I'm not sure exactly since when). I removed it because it no longer worked. > > Nevertheless, as I said, if there is a compelling reason to support it, > in addition to the shared library, I can look into doing as, as time > permits. > > Chris > > _______________________________________________ gs-devel mailing list [email protected] http://ghostscript.com/cgi-bin/mailman/listinfo/gs-devel