Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Archlinux Spring Setup

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
6/20/2014 6:53:57 PMUSrankHONKAHONK before revert after revert
6/20/2014 6:53:50 PMUSrankHONKAHONK before revert after revert
6/20/2014 6:39:09 PMUSrankHONKAHONK before revert after revert
Before After
1 Easy Mode 1 Easy Mode
2 ========= 2 =========
3 \n 3 \n
4 0.97 needs libsdl2 4 0.97 needs libsdl2
5 \n 5 \n
6 # pacman -S sdl2 6 # pacman -S sdl2
7 \n 7 \n
8 \n 8 \n
9 = flobby as my lobby client. 9 = flobby as my lobby client.
10 \n 10 \n
11 https://github.com/cleanrock/flobby 11 https://github.com/cleanrock/flobby
12 \n 12 \n
13 # pacman -S git gcc imagemagick fltk curl libxpm libxss boost 13 # pacman -S git gcc imagemagick fltk curl libxpm libxss boost
14 \n 14 \n
15 # git clone https://github.com/cleanrock/flobby.git 15 # git clone https://github.com/cleanrock/flobby.git
16 # cd flobby 16 # cd flobby
17 # git submodule update --init 17 # git submodule update --init
18 \n 18 \n
19 (gets pr-downloader) 19 (gets pr-downloader)
20 \n 20 \n
21 # cmake . 21 # cmake .
22 # make 22 # make
23 \n 23 \n
24 flobby binary is inside /src 24 flobby binary is inside /src
25 \n 25 \n
26 i don't see the advantage of creating a pacman pkg at this point - for lobbies or engines 26 i don't see the advantage of creating a pacman pkg at this point - for lobbies or engines
27 \n 27 \n
28 \n 28 \n
29 = spring engines/games/maps (auto) 29 = spring engines/games/maps (auto)
30 \n 30 \n
31 create /home/USERNAME/.spring and start flobby 31 create /home/USERNAME/.spring and start flobby
32 \n 32 \n
33 i had to update the location of pr-downloader in 33 i had to update the location of pr-downloader in
34 flobby to compiled location (pr-downloader/src/pr-downloader) 34 flobby to compiled location (pr-downloader/src/pr-downloader)
35 \n 35 \n
36 flobby will get map/engine/game automatically as of current update. It can look like it froze/crash while its downloading and only supports one download at a time. 36 flobby will get map/engine/game automatically as of current update. It can look like it froze/crash while its downloading and only supports one download at a time.
37 \n 37 \n
38 \n 38 \n
39 = manually add spring engines 39 = manually add spring engines
40 \n 40 \n
41 http://springrts.com/dl/buildbot/default/master/ 41 http://springrts.com/dl/buildbot/default/master/
42 \n 42 \n
43 just grab the pre-compiled portable engines you want. 0.91 and 0.96 seem the most common currently. 43 just grab the pre-compiled portable engines you want. 0.91 and 0.96 seem the most common currently.
44 \n 44 \n
45 eg. spring_96.0_minimal-portable-linux64-static.7z 45 eg. spring_96.0_minimal-portable-linux64-static.7z
46 \n 46 \n
47 if you don't have 7zip - plus others for good use 47 if you don't have 7zip - plus others for good use
48 # pacman -S p7zip zip rar unrar xarchiver 48 # pacman -S p7zip zip rar unrar xarchiver
49 \n 49 \n
50 if you want to be mr. linux then skip xarchiver and use command line 50 if you want to be mr. linux then skip xarchiver and use command line
51 \n 51 \n
52 extract them into .spring/engine/[engine version] eg. 0.91 52 extract them into .spring/engine/[engine version] eg. 0.91
53 \n 53 \n
54 start flobby and add them - 54 start flobby and add them -
55 \n 55 \n
56 name eg. 91.0 56 name eg. 91.0
57 browse for binary and unitsync 57 browse for binary and unitsync
58 hit save 58 hit save
59 \n 59 \n
60 rinse and repeat for other engines 60 rinse and repeat for other engines
61 click in white to deselect current engine and create a new entry 61 click in white to deselect current engine and create a new entry
62 \n 62 \n
63 = springlobby 63 = springlobby
64 \n 64 \n
65 The community repository has to be active 65 The community repository has to be active
66 \n 66 \n
67 http://wiki.archlinux.org/index.php/Pacman#Repositories 67 http://wiki.archlinux.org/index.php/Pacman#Repositories
68 \n 68 \n
69 After making sure that the local package database is up-to-date 69 After making sure that the local package database is up-to-date
70 \n 70 \n
71 # pacman -Sy 71 # pacman -Sy
72 \n 72 \n
73 springlobby is installed by 73 springlobby is installed by
74 \n 74 \n
75 # pacman -S springlobby 75 # pacman -S springlobby
76 \n 76 \n
77 There is also a springlobby-git package in AUR if you want to run bleeding edge of springlobby. 77 There is also a springlobby-git package in AUR if you want to run bleeding edge of springlobby.
78 \n 78 \n
79 \n 79 \n
80 \n 80 \n
81 = springlobby (source) 81 = springlobby (source)
82 \n 82 \n
83 springlobby has been broken/buggy for me for along time 83 springlobby has been broken/buggy for me for along time
84 \n 84 \n
85 https://github.com/springlobby/springlobby/wiki/Installfromsource 85 https://github.com/springlobby/springlobby/wiki/Installfromsource
86 \n 86 \n
87 # pacman -S openal curl gettext doxygen boost curl alure 87 # pacman -S openal curl gettext doxygen boost curl alure
88 \n 88 \n
89 Needs wxwidgets from AUR 89 Needs wxwidgets from AUR
90 \n 90 \n
91 https://aur.archlinux.org/packages/wxwidgets/ 91 https://aur.archlinux.org/packages/wxwidgets/
92 \n 92 \n
93 # tar -xvf wxwidgets.tar.gz 93 # tar -xvf wxwidgets.tar.gz
94 # cd wxwidgets 94 # cd wxwidgets
95 # makepkg -s 95 # makepkg -s
96 # pacman -U wxwidgets.(version).pkg.xz 96 # pacman -U wxwidgets.(version).pkg.xz
97 \n 97 \n
98 # git clone --recursive git://github.com/springlobby/springlobby.git 98 # git clone --recursive git://github.com/springlobby/springlobby.git
99 # cd springlobby 99 # cd springlobby
100 # git submodule update --init 100 # git submodule update --init
101 # cmake . 101 # cmake .
102 # make 102 # make
103 \n 103 \n
104 I usually skip this part and just run it from there ... then I don't have to go searching to remove it -- or you could use pacman to make a package to manage it 104 I usually skip this part and just run it from there ... then I don't have to go searching to remove it -- or you could use pacman to make a package to manage it
105 \n 105 \n
106 # make install 106 # make install
107 \n 107 \n
108 \n 108 \n