Packaging xLights for linux as AppImage

Now that I have xLights being built fine within docker (see Automatic testing of xLights builds via Travis-CI/Docker/Github) the next step is to package up the application as an appimage binary so that it can easily be run on varied linux systems.

It is being built based on Ubuntu Trusty and has been tested to work on Ubuntu 16.04, 16.10, Fedora 25 and OpenSuse 42.2 (and should hopefully work pretty much anywhere else as well)

The creation of the AppImage is done by the Recipe.appimage file that I included in the docker image.  This means that building of the appimage is simply:

$ $ d d o o c c k k e e r r p r u u l n l d - e n b a e m n e h a b m u / i x l l d i v g m h t d s e b e n h a m / x l i g h t s / b i n / b a s h R e c i p e . a p p i m a g e

I’ll break down the Recipe now to explain how it works:

First up we run the Recipe script to build xLights (as shown in previous post).

# ! R b e i c n i / p b e a s h

Next up we setup the environment ready for later on.  The $VERSION number is generated using the version number in the xLights_4_64bit.iss (which is where the version number is explicitly set for the windows install and so is a good/safe place to grab from).   If I am generating a release version (by passing ‘release’ as the command-line option) it will leave it at that.  If this is not a release version (such as for testing/development) then it will also add the short hash of the last commit.  This is handy so I can easily tell which commit the package was built from.

e c A C V i t e f x d P O E f h l i p P M R e s o $ = M S [ n e r { x I = t B L T ` " V V A i = g $ E E B S g ` r 1 R R A E h g e " S S S D t i p I I E I s t = O O D R A N N I } l p " = = R / o p r $ $ = x g V e { { / l e l V V x i r e E E L g - s a R R i h p i s S S g t r o e } } h s e n " - t - t $ s g t x ] { i y L C t = i O f g M o h M r t I m s T a _ } t 4 : _ ' 6 % 4 h b ' i t - . n i s 1 s ` | s e d - e ' s / ^ . * = / / g ' `

Now we install xLights into the target AppDir directory

r m m m k a - d k r i e f r i $ $ n { { s B B t A A a S S l E E l D D I I D R R E } } S / / T $ $ D A A I P P R P P = / / $ { B A S E D I R } / $ A P P / $ A P P . A p p D i r P R E F I X = / u s r

Okay, we have xLights installed in ${BASEDIR}/$APP/$APP.AppDir so the next step is to setup this directory ready to be packaged up.  To do this we import the functions.sh script which contains a bunch of handy functions needed for building AppImages

c w d g e $ t { / B - f A q u S n E h c D t t I t i R p o } s n / : s $ / . A s P r h P a / w . g i t h u b u s e r c o n t e n t . c o m / A p p I m a g e / A p p I m a g e s / m a s t e r / f u n c t i o n s . s h - O / f u n c t i o n s . s h

Lets put the appicons/desktop launcher in place ready to go

c c c c d p p p $ u u { s s / B r r u A / / s S s s r E h h / D a a s I r r h R e e a } / / r / i i e $ c c A o a P n n p P s s p / / / l $ h h i A i i c P c c a P o o t . l l i A o o o p r r n p / / s D 2 2 / i 5 5 x r 6 6 l x x i 2 2 g 5 5 h 6 6 t / / s a a . p p d p p e s s s / / k x x t l s o i c p g h h e . t d s u . l p e n . g p n . g .

Next we need to grab the AppRun binary (which is basically a wrapper which takes care of setting up all the environment so the binary inside the AppImage uses the right libraries/paths etc).   Since xLights needs a newer libstdc++.so.6 than is included in Ubuntu Trusty we needed a specially patched AppRun which allows for the bundling of the newer library without breaking systems which already have a newer library.  See https://github.com/darealshinji/AppImageKit-checkrt/ for details of why this is needed.

w g c e h t m o - d O + A x p p A R p u p n R u h n t t p s : / / g i t h u b . c o m / d a r e a l s h i n j i / A p p I m a g e K i t - c h e c k r t / r e l e a s e s / d o w n l o a d / c o n t i n u o u s / A p p R u n - p a t c h e d - x 8 6 _ 6 4

Now we need to find all the libraries needed by xLights and put them in place.  This is handled automatically by the copy_deps function we imported previously from functions.sh.  I have to manually move the pulseaudio libraries to the common directory (so AppRun doesn’t need to be modified further) and also remove libharfbuzz.* as it causes xLights to be unable to run if it is included.  I also manually copy libstdc++.so.6 to the special path as needed by the modified AppRun.  We finish up by stripping the libraries to save space.

e c s x o m m r m c d t p p o v m k p e r o y v d l i r _ e u u i / e p t d _ s s r u t e l r r s e u L p i / / - r _ s D s b l l p / b r _ i i l l / L ; b b u i a l I / / s b c i B c x x r k b R o 8 8 x l / A p 6 6 o 8 i * R y _ _ p 6 s Y _ 6 6 t _ t u _ d 4 4 i 6 e s P e - - o 4 d r A p l l n - / T s i i a l l H n n l i i = ; u u / n b . x x l u / / c - - i x * u o g g b - / s p n n s g * r y u u t n / _ / / d u l d p l c i e u i l b p l b i t / s s h b r : e a s u $ # a r t e L u f d D T d b c _ h i u + L r o z + I e / z . B e * . s R * o A r u . R u s 6 Y n r _ s / u P l s A t i r T o b / H / o e x p n 8 t s 6 i u _ o r 6 n e 4 a - l w l / e i l n i c u b a x s t - t c g d h n c u + i + n / d i r e c t o n e s

Almost done now. Just tell AppImageKit what the target launcher will be

g e t _ d e s k t o p i n t e g r a t i o n x l i g h t s

Final steps now.  First we check if we are running within Docker. This is needed so that the generate function knows to not use FUSE to mount the image (since FUSE doesn’t work properly within a standard docker container)

c # i d # # # # f e D } # # c O # A N # [ h C f # p o # [ o K i # p w # E # D # ! i R # i p # n _ # r a # $ B # c # ( d U # c k # c o I # o a # a c L # m g # t k D # p i # e = # l n # / r " # e g # p y # t # r e # e i # o s # t # c " # # / # a # 1 # s # / # # s # a # c # n # h # # e # A # d # p # # p # | # I # # m # h # a # e # g # a # e # d # # # # - # # n # # # # 1 # # # # | # # # # g # # r # # e # # p # # # # i # # n # # i # # t # # ) # # # # ] # # ] # # ; # # # # t # # h # # e # # n # # # # { # # # # # # # # # # # # # # # # # # #

And the very last step is to call generate_type2_appimage to actually create the appimage file itself

g e n e r a t e _ t y p e 2 _ a p p i m a g e

After all this is done we are left with a xLights.xxxxxx.AppImage file sitting in ${BASEDIR}/out - ready for uploading to the web and people to use!

For me I then scp them to my web server and wordpress will show the new file automatically at /xlights-linux/