Building a native (no X11) MacOSX binary: Difference between revisions

From Bluefish Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
A lot of information can be found here:
A lot of information can be found here:
http://gtk-osx.sourceforge.net/
http://gtk-osx.sourceforge.net/
follow the instructions to get the gtk core up and running
== jhbuild configuration ==


a jhbuild section for bluefish looks like this:
a jhbuild section for bluefish looks like this:
Line 20: Line 24:
  </autotools>
  </autotools>
----------------------------------
----------------------------------
== Building ==
pcre.h is missing on OSX, but libpcre is available. You can copy the pcre.h file from a different computer to ~/gtk/inst/include/pcre.h
== Creating a package ==
todo
== Better MacOSX integration ==
todo

Revision as of 17:44, 8 March 2010

This is work in progress.

A lot of information can be found here: http://gtk-osx.sourceforge.net/

follow the instructions to get the gtk core up and running

jhbuild configuration

a jhbuild section for bluefish looks like this:


<repository type="tarball" name="bluefish" href="http://www.bennewitz.com/bluefish/stable/source/"/>
<autotools id="bluefish">
<branch module="bluefish-2.0.0.tar.bz2" version="2.0.0" repo="bluefish" md5="ac9b1e8ef6d5691718a0daa6c78d5618" size="3287346"/><dependencies>
<dep package="intltool"/>
<dep package="gtk+"/>
<dep package="glib"/>
<dep package="libxml2"/>
</dependencies>
<suggests>
<dep package="enchant"/>
<dep package="gucharmap"/>
</suggests>
</autotools>

Building

pcre.h is missing on OSX, but libpcre is available. You can copy the pcre.h file from a different computer to ~/gtk/inst/include/pcre.h

Creating a package

todo

Better MacOSX integration

todo