Re: [gtk-osx-users] Module From Scratch - Dependencies
- From: John Ralls <jralls ceridwen us>
- To: David Lowe <doctorjlowe twc com>
- Cc: gtk-osx-users-list gnome org
- Subject: Re: [gtk-osx-users] Module From Scratch - Dependencies
- Date: Wed, 17 May 2017 18:01:04 -0700
On May 17, 2017, at 5:32 PM, David Lowe <doctorjlowe twc com> wrote:
Greetings!
I’m ‘porting’ a package from Fink. One advantage of this is that i already have a good idea of the
dependencies needed, and just need to find their analogs in jhbuild modules. Here’s a list:
BuildDepends: <<
atk1,
bzip2-dev,
cairo,
fontconfig2-dev,
freetype219,
gettext-tools,
glib2-dev,
glitz,
gtk+2-dev,
libcurl4,
libgettext8-dev,
libiconv-dev,
liblzma5,
pango1-xft2-ft219-dev,
pkgconfig,
readline6,
sdl,
sdl-mixer,
x11-dev,
xft2-dev
<<
However, grepping in the moduleset directory for, let’s say, ‘atk’ comes up empty. Some of these
have to be provided by meta-gtk-osx-core, right? If so, which ones??
Yes, atk is part of meta-gtk-osx-core and meta-gtk-osx-gtk3. atk1 isn't, but it's probably just a Finkism for
atk. There are a bunch of those in your list, including anything ending with "dev" and anything with a
version. jhbuild builds libraries from source so you always get the headers along with the libraries. Grep
for only the project name, e.g. 'gtk+'--or better 'id=".*gtk+.*"'. To see what will build when you specify a
meta-module, list the module: `jhbuild list meta-gtk-osx-core`.
Beware when porting from Fink that (last I checked, anyway) Fink builds only X11 variants and gtk-osx builds
only Quartz variants. If the application you're trying to port uses X11 or Xft directly (bypassing gtk) then
it won't build under gtk-osx. MacPorts supports both so its package file for the app might be a better
starting point.
Aside from those two, gtk-osx doesn't have modules for glitz, sdl, sdl-mixer, or libcurl. The rest will be
built by bootstrap, meta-gtk-osx-bootstrap, meta-gtk-osx-freetype, and meta-gtk-osx-core.
And BTW, gtk-osx is focussed on developers who want to ship their own applications as Mac application
bundles. It's not intended for users who simply want to run some random Linux app on their Macs: That's what
Homebrew and MacPorts are for.
Regards,
John Ralls.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]