forked from f-spot/f-spot
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README
51 lines (33 loc) · 1.63 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
F-Spot Photo Manager
http://f-spot.org/
Requirements:
- GNOME development libraries 2.4 or later,
http://www.gnome.org
- Mono 2.2 or later, http://www.go-mono.net
- gtk-sharp 2.12.2 or later, http://www.go-mono.net
- Sqlite 2.8.6 or later
- liblcms 1.12 or later, http://www.littlecms.com/
- hicolor-icon-theme 0.10 or later, http://icon-theme.freedesktop.org/wiki/HicolorTheme
- taglib-sharp 2.0.3.7 or later, https://github.com/mono/taglib-sharp
- dbus-sharp 0.7 or later, https://github.com/mono/dbus-sharp
- dbus-sharp-glib 0.5 or later, https://github.com/mono/dbus-sharp-glib
To compile, just go through the normal autogen/configure stuff and
then make install.
To launch F-Spot, run $(prefix)/bin/f-spot.
With MonoDevelop:
If you want to use MonoDevelop to build and run F-Spot here are notes about that process.
There are a few steps you have to run before you can open MonoDevelop:
1. sh autogen.sh (on ubuntu you have to do ./autogen.sh)
2. cd build; make
3. cd ..; cp hyena.patch lib/Hyena
4. cd lib/Hyena; patch -p1 < hyena.patch
5. cd ../libfspot; make
6. sudo make install (this will install the libfspot.so files)
The hyena patch is just a temporary fix for now.
This will build a couple tools in ./build that are needed to build the projects
in ./lib. Unfortunately, the f-spot.exe.config file points to whatever prefix
you gave during 'sh autogen.sh'. You could copy the files from
./lib/libfspot/.libs to ./bin and edit f-spot.exe.config, but it'll get
overwritten with each build.
Once these two directories are built you can now open monodevelop and build
and run f-spot from there.