Difference between revisions of "Solaris"
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
== Gnucash on Solaris== | == Gnucash on Solaris== | ||
+ | |||
+ | The following are the programs that you will need to compile on Solaris 10 11/06 x86 edition to be able to compile and use Gnucash 2.2.0 | ||
+ | |||
+ | |||
+ | <code><pre> | ||
+ | |||
+ | gtkthml | ||
+ | ORBit2 | ||
+ | |||
+ | GOffice - without gnome | ||
+ | PCRE - Perl Compatible Regular Expressions --with-utf8 | ||
+ | libgnomeprint | ||
+ | libgsf | ||
+ | |||
+ | libglade | ||
+ | |||
+ | gtk | ||
+ | pango | ||
+ | cairo | ||
+ | atk | ||
+ | |||
+ | postgresql | ||
+ | |||
+ | guile 1.6.8 | ||
+ | swig - update vicinity path on all *.init files | ||
+ | gmp | ||
+ | libtool | ||
+ | |||
+ | glib | ||
+ | pkg-config | ||
+ | |||
+ | aqbanking | ||
+ | libofx .8.3 | ||
+ | OpenSP 1.5.2 | ||
+ | libchipcard | ||
+ | gwenhywfar | ||
+ | ncurses | ||
+ | ktoblzcheck | ||
+ | ctypes | ||
+ | </pre></code> | ||
+ | |||
+ | My PKG_CONFIG_PATH is: | ||
+ | |||
+ | /opt/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig | ||
+ | |||
+ | |||
+ | |||
+ | If the startup Druid shows an empty box then add: | ||
+ | |||
+ | /usr/lib/libglade/2.0/libgnome.so via crle or LD_LIBRARY_PATH | ||
+ | |||
+ | |||
+ | Almost everything is a clean compile with no modifications needed. | ||
+ | |||
+ | |||
+ | For Goffice just add the Environment Variable that it complains about to existing paths and it will compile easily. There is only one to set so it's no big deal. | ||
+ | |||
+ | |||
+ | According to GNUcash some of the Sun supplied GNOME programs for JDS are out of date, therefore you will need to compile up current versions. | ||
+ | |||
+ | |||
+ | [http://www.blastwave.org Blastwave] has a version that you can obtain using their tools if you have no idea how to compile code. | ||
+ | |||
+ | |||
+ | [http://www.ilkda.com/compile/index.htm Sun Country's How To Compile C Code] is a starting point to learn how to compile C code. This in no way, shape, or form, tries to tell you how to actually write a single line of code. | ||
+ | |||
+ | |||
+ | I used to make the Solaris packages for GNUcash but will probably NOT do that for this version. This version compiles easily once all of the prerequisites are in place. The prerequisites are listed in reverse order. Start with the last one and work your up to the top. | ||
+ | |||
+ | |||
+ | alan pae (alanpae at ilkda dot com) | ||
+ | |||
+ | [[User:Alanpae|Alanpae]] 21:13, 9 August 2007 (EDT) |
Latest revision as of 01:13, 10 August 2007
Gnucash on Solaris
The following are the programs that you will need to compile on Solaris 10 11/06 x86 edition to be able to compile and use Gnucash 2.2.0
gtkthml
ORBit2
GOffice - without gnome
PCRE - Perl Compatible Regular Expressions --with-utf8
libgnomeprint
libgsf
libglade
gtk
pango
cairo
atk
postgresql
guile 1.6.8
swig - update vicinity path on all *.init files
gmp
libtool
glib
pkg-config
aqbanking
libofx .8.3
OpenSP 1.5.2
libchipcard
gwenhywfar
ncurses
ktoblzcheck
ctypes
My PKG_CONFIG_PATH is:
/opt/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/sfw/lib/pkgconfig
If the startup Druid shows an empty box then add:
/usr/lib/libglade/2.0/libgnome.so via crle or LD_LIBRARY_PATH
Almost everything is a clean compile with no modifications needed.
For Goffice just add the Environment Variable that it complains about to existing paths and it will compile easily. There is only one to set so it's no big deal.
According to GNUcash some of the Sun supplied GNOME programs for JDS are out of date, therefore you will need to compile up current versions.
Blastwave has a version that you can obtain using their tools if you have no idea how to compile code.
Sun Country's How To Compile C Code is a starting point to learn how to compile C code. This in no way, shape, or form, tries to tell you how to actually write a single line of code.
I used to make the Solaris packages for GNUcash but will probably NOT do that for this version. This version compiles easily once all of the prerequisites are in place. The prerequisites are listed in reverse order. Start with the last one and work your up to the top.
alan pae (alanpae at ilkda dot com)
Alanpae 21:13, 9 August 2007 (EDT)