1 |
On Wednesday 17 April 2002 12:02 am, Jared H. Hudson wrote: |
2 |
> > Should I compile all 4 of them? Yes doing this would take some bash magic |
3 |
> > but not too much. If I should do all four of them what naming convention |
4 |
> > should I use for the differant executables? Some thing like nethackQt |
5 |
> > nethackGnome? |
6 |
> |
7 |
> I would say yes, do this. If you need an example, look at: |
8 |
> app-editors/vim for example, it builds a GUI version and a non-GUI version. |
9 |
> |
10 |
> It's really not that hard. The way I would lay it out is: |
11 |
> |
12 |
> # handle use options common to all types |
13 |
> use foo && myconf="$myconf --enable-foo" |
14 |
> use foo2 && myconf="$myconf --enable-foo2" |
15 |
> |
16 |
> # handle first possible build type |
17 |
> if [ "`use gnome`" ]; |
18 |
> then |
19 |
> ./configure --prefix=/usr --host=$CHOST \ |
20 |
> --mandir=/usr/share/man --enable-gtk --enable-gnome $myconf \ |
21 |
> |
22 |
> || die "gnome & gtk configure failed" |
23 |
> |
24 |
> emake || die "gnome & gtk make failed" |
25 |
> |
26 |
> mv src/foo src/gfoo |
27 |
> fi |
28 |
> |
29 |
> # handle second possible build type |
30 |
> if [ "`use kde`" ]; |
31 |
> then |
32 |
> ./configure --prefix=/usr --host=$CHOST \ |
33 |
> --mandir=/usr/share/man --enable-qt --enable-kde $myconf \ |
34 |
> |
35 |
> || die "kde & qt configure failed" |
36 |
> |
37 |
> emake || die "kde & qt make failed" |
38 |
> |
39 |
> mv src/foo src/kfoo |
40 |
> fi |
41 |
> |
42 |
> # handle normal build type |
43 |
> ./configure --prefix=/usr --host=$CHOST \ |
44 |
> --mandir=/usr/share/man $myconf \ |
45 |
> |
46 |
> || die "normal configure failed" |
47 |
> |
48 |
> emake || die "normal make failed" |
49 |
> |
50 |
> |
51 |
> My example may not be perfect, but you get the idea (I hope) |
52 |
> |
53 |
Kinda of what I was looking at doing. The differance is that basicly I have to |
54 |
have a clean source directory for each step because you have to modify the |
55 |
make files as nethack does not use automake so I have a patch for each option |
56 |
that has to be applied to the clean sources. And of couse each of them will |
57 |
install on top of the other when you get to the install process so I was |
58 |
looking at handling that myself so things would be done right as far as each |
59 |
version goes that is. It is kinda of a pain but doable. I will take a look at |
60 |
the vim ebuild though as I'm still not real strait on some of the vars used |
61 |
in the ebuild files. I gues I need to reread the howto again. |
62 |
|
63 |
Richard jackson |