aboutsummaryrefslogtreecommitdiff
path: root/gui/themebrowser.cpp
diff options
context:
space:
mode:
authorHubert Maier2016-01-03 13:44:24 +0200
committerHubert Maier2016-01-03 13:44:24 +0200
commit44e2256e731c5bbadb9ac23736e340aac1ccba6c (patch)
treee23ec51d4b8a7ad2f7c8d35a33655fc53959d33e /gui/themebrowser.cpp
parent35e526d34b4306739938a80c329a24b294a1860d (diff)
downloadscummvm-rg350-44e2256e731c5bbadb9ac23736e340aac1ccba6c.tar.gz
scummvm-rg350-44e2256e731c5bbadb9ac23736e340aac1ccba6c.tar.bz2
scummvm-rg350-44e2256e731c5bbadb9ac23736e340aac1ccba6c.zip
AMIGAOS: Static builds preferred
Reasons: - Shared objects aren't really shared on AmigaOS (Once two programs load the same .so, it will be loaded twice into memory instead of sharing the already available one) - To make the program run for everyone i need to provide a subdir (SObjs/) which holds all the .so's used while compiling, otherwise some people have to go hunting for the correct .so's online. (That completely defies the use of "shared objects") Even worse is the fact that, if users have older .so's installed, they might experience crashes. - There is no benefit in building ScummVM with shared objects, because even *if* a new lib version is available as an .so it won't be mandatory to immediately switch to it, because the code probably won't take advantage of it as fast. In short: Switchting to static builds to reduce user grief, crash reports and as a bonus have ScummVM start a little faster.
Diffstat (limited to 'gui/themebrowser.cpp')
0 files changed, 0 insertions, 0 deletions