Difference between revisions of "Compiling Mudlet"

From Mudlet
Jump to navigation Jump to search
(Undo revision 2306 by Chris (talk))
 
(459 intermediate revisions by 32 users not shown)
Line 1: Line 1:
 
{{TOC right}}
 
{{TOC right}}
  
{{note}} Mudlet uses Qt 5.2 now. In cases where an earlier Qt version is mentioned, please use Qt 5.2.
+
If you just want to use Mudlet, you can skip these steps, and use one of the already ready (pre-compiled) installers [https://www.mudlet.org/download ready for download].
  
== Compiling on Ubuntu 12.10 / 13.04 ==
+
Otherwise, hop in for new adventure!
  
 +
[[File:Easy Mudlet code understanding.png|400px|none]]
  
'''1. Install GIT'''
+
= Compiling =
sudo apt-get install git
 
  
'''2. Installing the needed packages'''
+
== Compiling on Ubuntu ==
  
sudo apt-get install build-essential qt4-dev-tools lua5.1 liblua5.1-0-dev libpcre3-dev libboost-dev zlib1g-dbg zlib1g-dev libyajl2 \
+
These instructions will get you setup compiling on Ubuntu. Need a hand? Join us on Mudlet's [https://discord.gg/BwgJpMj Discord] or [http://forums.mudlet.org/viewforum.php?f=7 forums].
libyajl-dev libyajl2-dbg liblua5.1-rex-pcre0 liblua5.1-sql-sqlite3-2 libphonon-dev libhunspell-dev libzip-dev liblua5.1-zip0 \
 
liblua5.1-filesystem0
 
  
'''3. get mudlet source'''
+
===Ubuntu 22.04 & later===
git clone git://git.code.sf.net/p/mudlet/code
+
Following instructions will work on Ubuntu 22.04 as well as all its flavours and derivatives (such as KDE Neon, for example)
{old location git://mudlet.git.sourceforge.net/gitroot/mudlet/mudlet no longer valid}
+
Important thing is to have ''Universe'' repository enabled in your package manager. (on Ubuntu you will have all the repositories that you need already enabled by default.)
  
'''4. goto the mudlet src folder'''
+
'''1. necessary dependencies'''
cd mudlet/src
 
  
'''5.a edit src.pro like so (for 32bit):'''
+
Majority of required dependencies can be obtained from repositories, and can be installed with following command:
  
replace the corresponding part near the beginning of the file with this:
+
  sudo apt install ubuntu-restricted-extras qtcreator build-essential git zlib1g-dev libhunspell-dev \
 +
  libpcre3-dev libzip-dev libboost-dev libboost-all-dev libyajl-dev libpulse-dev libpugixml-dev \
 +
  liblua5.1-0-dev lua-filesystem lua-zip lua-sql-sqlite3 luarocks ccache lua5.1 libsecret-1-dev \
 +
  libglu1-mesa-dev mesa-common-dev libglib2.0-dev libgstreamer1.0-dev libqt5opengl5-dev cmake \
 +
  qt6-multimedia-dev libqt6core5compat6 qt6-tools-dev qtkeychain-qt6-dev qt6-l10n-tools ninja-build \
 +
  qt6-tools-dev-tools libqt6core5compat6-dev qttools5-dev qtmultimedia5-dev qt6-speech-dev
  
LIBLUA = -llua5.1
+
'''1.1 Ubuntu 24.04:'''
!exists(/usr/lib/i386-linux-gnu/liblua5.1.a):LIBLUA = -llua
 
 
# automatically link to LuaJIT if it exists
 
exists(/usr/lib/i386-linux-gnu/libluajit-5.1.a):LIBLUA = -L/usr/lib/i386-linux-gnu/ -lluajit-5.1
 
  
 +
<code>sudo apt install qt6-multimedia-dev</code>
  
'''5.b edit src.pro like so (for 64bit):'''
+
Few of required Lua modules are not available in official repositories, so they have to be installed using ''luarocks''
 +
  sudo luarocks install lcf
 +
  sudo luarocks install luautf8
 +
  sudo luarocks install lua-yajl
 +
  sudo luarocks install lrexlib-pcre
  
replace the corresponding part near the beginning of the file with this:
+
'''2. obtaining the source code'''
  
LIBLUA = -llua5.1
+
Obtain the latest in-development code with:
!exists(/usr/lib/x86_64-linux-gnu/liblua5.1.a):LIBLUA = -llua
+
  git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
+
  mkdir Mudlet/build
# automatically link to LuaJIT if it exists
+
  cd Mudlet/build
exists(/usr/lib/x86_64-linux-gnu/libluajit-5.1.a):LIBLUA = -L/usr/lib/x86_64-linux-gnu/ -lluajit-5.1
 
  
'''6. address the removal of yajl1 from the offical repos (thanks to Blackice89 for this info from the arch compile guide)'''
+
'''3. compiling the code'''
wget http://vrac.kadarniad.fr/lua_yajl2.c
+
  cmake .. -G Ninja
for i in *.{cpp,h} ; do sed -i 's/#include <phonon>/#include <phonon\/MediaObject>\n#include <phonon\/AudioOutput>/' $i ; done
+
  ninja
sed -i 's/lua_yajl1.c/lua_yajl2.c/' TLuaInterpreter.cpp
 
sed -i 's/-lhunspell/-lhunspell-1.3/' src.pro
 
sed -i 's/lua_yajl1.c/lua_yajl2.c/' src.pro
 
sed -i '/MOC_DIR.*/i QMAKE_MOC += -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED' src.pro
 
sed -i '/.*unix:LIBS.*/a -lz \\' src.pro
 
  
'''6. Alternative Step 6'''
+
4. '''installing compiled code'''
Remove the downloaded yajl libraries:
+
 
   sudo apt-get remove libyajl2 libyajl-dev libyajl2-dbg
+
After successful code compilation, next few commands will install resulting binaries, desktop file for menus and appropriate icon.
  Download yajl from here:
+
  sudo make install
  http://github.com/lloyd/yajl/tarball/1.0.12
+
  sudo cp ../mudlet.png /usr/share/pixmaps
  in the directory it was extracted to, run:
+
  sudo cp ../mudlet.desktop /usr/share/applications
  configure (you may need to install ruby for this, sudo apt-get ruby for that)
+
 
make
+
5. '''optional additional software'''
sudo make install
+
 
edit src.pro again, and replace -lyajl with:
+
One of the major reasons for compiling Mudlet from source is the ability to unlock more features that are not enabled in official AppImage.
    -L/usr/local/lib/ \
+
Manual compilation will resolve the issues with sound by using system provided libraries, as well as enable more detailed theming of Mudlet application itself.
    -lyajl \
+
However, do take note that Mudlet is a Qt based program, and that theming will not 'just work' in GTK based desktop environments (Gnome, XFCE, MATE, Budgie).
 +
  sudo apt install qt5ct
 +
will install a tool for configuration of look and feel of Qt programs inside those desktop environments.
 +
Users of Qt based Desktop environments (KDE Plasma, LXQT) can simply use settings provided by environment itself.
 +
 
 +
Many of Qt widget styles and color schemes are available in official repositories, and will make Mudlet better.
 +
 
 +
6. '''Mudlet on Wayland'''
 +
 
 +
Mudlet compiled like this will run and work on Wayland, however, there are a few quirks with Keybidings (Numpad may not work as expected).
 +
Until that is resolved you may wish to start mudlet with:
 +
  QT_QPA_PLATFORM=xcb mudlet
 +
(enter in terminal or simply change the Exec= line in /usr/share/applications/mudlet.desktop)
 +
 
 +
7. '''uninstallation'''
 +
 
 +
You can reverse the process described in this guide with following command:
 +
 
 +
   sudo rm -fr /usr/bin/mudlet /usr/share/mudlet /usr/share/applications/mudlet.desktop /usr/share/pixmaps/mudlet.png
 +
 
 +
===Other Ubuntu Versions===
 +
 
 +
Most of the installation instructions for 22.04 should work for older versions as well. Of note is the required version of Qt, which is 5.14. If your used version of Ubuntu only supplies older
 +
Qt versions, have a look at [https://launchpad.net/~beineri Stephan Binners PPAs], which supplies a whole range of packages for different Ubuntu versions. Be sure to read the installation and
 +
usage instructions as Qt is installed to /opt and requires sourcing a script to set up.
 +
 
 +
== Compiling on Chrome OS ==
 +
 
 +
These instructions will get you setup compiling on Chrome OS. Need a hand? Join us on Mudlet's [https://discord.gg/BwgJpMj Discord] or [http://forums.mudlet.org/viewforum.php?f=7 forums].
 +
 
 +
'''1. Install dependencies'''
 +
 
 +
sudo apt install git build-essential \
 +
  lua5.1 liblua5.1-0-dev libpcre3-dev libboost-dev zlib1g-dev cmake \
 +
  libhunspell-dev lua-rex-pcre2 lua-sql-sqlite3 lua-filesystem lua-zip libyajl-dev \
 +
  libzip-dev libglu1-mesa-dev ccache libpugixml-dev mesa-common-dev qtcreator \
 +
  libpulse-dev libglib2.0-dev luarocks libboost-all-dev libsecret-1-dev \
 +
  ninja-build libsecret-1-dev qt6-tools-dev qt6-5compat-dev qt6-multimedia-dev
 +
sudo luarocks install luautf8
 +
  sudo luarocks install lua-yajl
 +
 
 +
'''3. Get Mudlet source'''
 +
 
 +
git clone --recursive https://github.com/Mudlet/Mudlet.git mudlet
 +
 
 +
'''4. Create a build directory'''
 +
 
 +
cd mudlet
 +
  mkdir build && cd build
 +
 
 +
'''5. Run the following command '''
 +
 
 +
cmake .. -G Ninja
 +
 
 +
'''then:'''
 +
 
 +
  ninja -j 2
 +
 
 +
'''5. Start the application you have just compiled - enjoy'''
 +
 
 +
src/mudlet
 +
 
 +
== Compiling on macOS ==
 +
 
 +
These instructions will get you setup compiling on macOS. Need a hand? Join us on Mudlet's [https://discord.gg/BwgJpMj Discord server] or [http://forums.mudlet.org/viewforum.php?f=7 forums] otherwise.
 +
 
 +
 
 +
'''1. Install prerequisites'''
 +
 
 +
Install [https://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12 XCode], command line tools for XCode, and [http://brew.sh HomeBrew].
 +
 
 +
Once everything is installed, do:
 +
 
 +
  brew doctor
 +
  brew update
 +
  brew install git
 +
 
 +
'''2. Get Mudlet source'''
 +
  git clone --recursive https://github.com/Mudlet/Mudlet.git
 +
 
 +
'''3. Go to the parent of the mudlet "src" folder and create (if necessary) a build subdirectory (this is so that we can build out of source which keeps the source code clean)'''
 +
  cd Mudlet && mkdir build
  
'''7. run the following commands'''
+
'''3. Setup your environment'''
 +
  ./CI/travis.osx.before_install.sh
 +
  ./CI/travis.osx.install.sh
  
qmake-qt4
+
  luarocks config lua_version 5.1
make
+
  eval `luarocks path --lua-version=5.1`
./mudlet
+
For the following, one may have to add <code>''_DIR="/opt/homebrew/"''</code> such as <code>PCRE_DIR="/opt/homebrew/"</code> or <code>ZIP_DIR="/opt/homebrew/"</code> if the installation could not find header files.
 +
  luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install lrexlib-pcre PCRE_DIR=`brew --prefix pcre`
 +
  brew install sqlite
 +
  luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luasql-sqlite3 SQLITE_DIR=`brew --prefix sqlite`
 +
  luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luautf8
 +
  luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luafilesystem
 +
  luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install lua-zip ZIP_DIR=`brew --prefix libzip`
  
 +
  brew install boost
 +
OK to answer yes to delete files if prompted for the <code>rm</code> command above.
  
'''8. enjoy'''
+
'''4. Run the following commands'''
  
== Compiling on Debian 7.1 ("Wheezy") ==
+
  cd build
 +
  cmake ../../Mudlet -DCMAKE_PREFIX_PATH=`brew --prefix qt5`
 +
  make -j `sysctl -n hw.ncpu`
  
  
'''1. Install GIT. '''
+
'''5. Enjoy'''
In a terminal window type:
+
 
sudo apt-get install git
+
The mudlet.app is now available in <code>src/</code> for launching:
  
 +
  open src/Mudlet.app
  
'''2. Install needed Debian packages. '''
+
'''6. Qt Creator setup'''
Only the development [-dev] ones are shown here, as this should also get the associated main packages auto-magically if not already present on the system:
 
sudo apt-get install ''"compiler packages & qt-sdk packages"''
 
liblua5.1-0-dev libboost-dev libhunspell-dev libphonon-dev lua-zlib-dev
 
libzip-dev libyajl-dev lua-rex-pcre lua-zip lua-filesystem lua-sql-sqlite3
 
  
N.B. "compiler packages & qt-sdk packages" could probably be "g++", "libstdc++6" and "qmake" to pull in the default GCC C++ compiler and associated libraries and qt Make system; "qt4-dev-tools" to pull in the development Qt libraries; "gdb" if you are planning on doing any debugging and "qtcreator" to provide a nice IDE to do it all in. The last four dependences are not required to compile the code but their absence will show up in error messages from the LUA subsystem as connection is made to a MUD and the session starts up, unlike other dependences only the main files seem to be required (it not being necessary to include the development [-dev] packages.)
+
No Lua installation is found, despite it existing on your system? Launch Qt Creator by doing <code>open /Applications/Qt Creator.app</code> (location depends on how you installed it).
  
'''3. Build and install non-Debian packages. '''
+
Receiving a <code>No rule to make target ... libQt5UiTools_debug.a</code> error? A workaround is to [https://bugreports.qt.io/browse/QTBUG-81251?focusedCommentId=538705&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-538705 symlink a file].
Which presently is only the C++/Qt Zip library "quazip", download the latest version [http://sourceforge.net/projects/quazip/files/latest/download?source=files quazip-0.5.1.zip].
 
After unzipping to a new directory of your choice add: "QMAKE_CXXFLAGS += -fpermissive" near the top of the "./qztest/qztest.pro" file to change errors to warnings on assigning some gzFile pointers to void ones in the test suite - this seems to be needed to get the whole thing to compile (though the test suite isn't necessary for compiling Mudlet purposes).  After making that change in a terminal window run "qmake" on the quazip project file in the base of the quazip project directory tree to update the subdirectory project files.  After building (with "make") in that base directory use "sudo make install" to install the newly constructed files in your system - this puts headers in /include and libraries in /lib of your file-system so some tweaking in the last couple of bits of this section could avoid the need to manually move the library and the three symbolic links from /lib to /usr/local/lib/ and the header files from /includes to /usr/local/includes/.
 
  
'''4. Get the Mudlet source. '''
+
Mudlet in Qt Creator is not launching due to <code>dyld: Symbol not found: __cg_jpeg_resync_to_restart</code>? See [https://stackoverflow.com/a/44851430/72944 here] for a workaround.
In a terminal window:
 
git clone git://git.code.sf.net/p/mudlet/code
 
  
'''5. Compile the Mudlet source. '''
+
'''7. (Optional) Discord Integration on ARM64'''
In that terminal window:
 
  qmake
 
  make
 
or if you've got qtcreator set up once you've opened the Mudlet project file which is "./src/src.pro" relative to wherever you had Git clone the code in the previous step, hit the "build src.pro" and go and grab a hot drink or whatever whilst the code is compiled...!
 
  
'''6. Run Mudlet, and Enjoy. '''
+
ARM64 binaries are not available libdiscord-rpc so you need to compile and combine it with the existing x86_64 binary into a universal binary.
From a terminal window run the mudlet executable, as it is relative to where you had Git clone the code to this will be the file:
 
./src/mudlet
 
  
Like other systems documented here, it may not be possible to do a "make install" to make this executable work for all users of the system on which it has just been built. At the point of writing the default Qt libraries provided for Debian "Wheezy" are version 4.8.2 which may not match the ones of the Qt-sdk recommended by the Mudlet makers. In the event of problems in that area you may be recommended to build that specific version of the libraries and recompile Mudlet with them - fortunately Qt-Creator does make the latter part relatively straightforward.
+
<syntaxhighlight lang="bash">
 +
git clone --single-branch --branch v3.3.0 https://github.com/discord/discord-rpc.git
 +
cd discord-rpc
 +
python build.py libs --shared
 +
lipo ./builds/install/osx-dynamic/lib/libdiscord-rpc.dylib /path/to/existing/x86_64/libdiscord-rpc.dylib -output libdiscord-rpc.dylib -create
 +
// verify that it's a universal binary:
 +
otool -L libdiscord-rpc.dylib
 +
// check it in to source control
 +
</syntaxhighlight>
  
 +
'''8. Troubleshooting'''
 +
If you exhaust all efforts to get YAJL to compile on your local system with homebrew, [https://github.com/lloyd/yajl/ clone from the YAJL repository] then  <code>./configure && sudo make install</code>.
  
== Compiling on Debian 'Sid' ==
+
== Compiling on Debian ==
  
 
'''1. Install required packages from main repo.'''
 
'''1. Install required packages from main repo.'''
 
 
  $ sudo apt-get install build-essential lua5.1 liblua5.1-0-dev libpcre3-dev libboost-dev zlib1g-dbg zlib1g-dev libyajl2 \
+
  sudo apt-get install build-essential git liblua5.1-0-dev zlib1g-dev libhunspell-dev libpcre3-dev \
  libyajl-dev libyajl2-dbg libphonon-dev libhunspell-dev lua-filesystem libquazip0-dev libzzip-dev lua-rex-pcre lua-zip \
+
  libzip-dev libboost-dev libyajl-dev libpulse-dev libsecret-1-dev lua-rex-pcre2 lua-filesystem lua-zip \
  lua-sql-sqlite3 qt5-default git
+
  lua-sql-sqlite3 qt5-qmake qtmultimedia5-dev qttools5-dev luarocks ccache libpugixml-dev
  
 +
sudo luarocks install luautf8
 +
sudo luarocks install lua-yajl
 +
sudo luarocks install lrexlib-pcre
  
 
'''2. Grab latest Mudlet source.'''
 
'''2. Grab latest Mudlet source.'''
 
 
  $ cd ~ && mkdir projects && cd projects && git clone git://git.code.sf.net/p/mudlet/code mudlet
+
  mkdir ~/projects && cd ~/projects && git clone --recursive https://github.com/Mudlet/Mudlet.git mudlet
 +
 
 +
'''3. Build Mudlet.'''
 +
 
 +
cd ~/projects/mudlet/src
 +
 
 +
qmake
 +
 
 +
make
 +
 
 +
sudo make install
 +
 
 +
'''4. (Optional) Discord library'''
 +
 
 +
If you get the following error;
 +
 
 +
Could not find Discord library - searched in:
 +
 
 +
you need to specify the discord library in your build. Run the following, changing the path where necessary;
 +
 
 +
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/user/mudlet-dev/Mudlet/3rdparty/discord/rpc/lib/
 +
 
 +
and recompile.  You should see
 +
 
 +
Discord integration loaded. Using functions from: "libdiscord-rpc.so"
  
 +
== Compiling on Raspberry Pi OS ==
  
'''3. Build latest libzip.'''
+
These instructions will get you compiling and running Mudlet on Raspberry Pi OS (Buster). Need a hand? Join us on Mudlet's [https://discord.gg/BwgJpMj Discord] or [http://forums.mudlet.org/viewforum.php?f=7 forums].
+
 
  $ cd mudlet/src && wget http://www.nih.at/libzip/libzip-0.11.1.tar.gz
+
''' 1.a Install apt dependencies '''
 +
 
 +
sudo apt-get update
 +
sudo apt-get install build-essential git liblua5.1-dev zlib1g-dev libhunspell-dev libpcre3-dev \
 +
  libzip-dev libboost-graph-dev libyajl-dev libpulse-dev lua-rex-pcre2 lua-filesystem lua-zip \
 +
  lua-sql-sqlite3 qt5-assistant qtmultimedia5-dev qttools5-dev luarocks ccache libpugixml-dev cmake
 +
 
 +
 
 +
[[File:Apt-get-install-y-n.png|center|thumb|installing apt dependencies]]
 +
 
 +
''' 1.b Install luarocks dependencies '''
 +
 
 +
  sudo luarocks install luautf8
 +
sudo luarocks install lrexlib-pcre
 +
sudo luarocks install lua-yajl YAJL_LIBDIR=`find /usr -name "libyajl.so" -printf '%h\n'` YAJL_INCDIR=/usr/include
 +
 
 +
 
 +
[[File:After-luarocks-dependencies.png|center|thumb|after luarocks dependencies]]
 +
 
 +
''' 2. Get Mudlet source '''
 +
 
 +
mkdir ~/source && cd ~/source
 +
git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 +
 
 +
[[File:After-get-mudlet-source.png|center|thumb|After cloning]]
 +
 
 +
''' 3. Create a build directory '''
 +
 
 +
  cd Mudlet && mkdir build && cd build
 +
 
 +
''' 4. Run the following commands to build '''
 +
 
 +
WITH_UPDATER=NO WITH_3DMAPPER=NO qmake ../src/mudlet.pro
 +
 
 +
:If you get a response along the lines of:
 +
 
 +
qmake: could not find a Qt installation of ''
 +
 
 +
:then you likely have ''qtchooser'' present in your system that allows for both Qt4 and Qt5 (or more than one Qt5 version) and it modifiers qmake and some other Qt development programs to take an additional argument to specify which version to use. In that case you should use:
 +
 
 +
WITH_UPDATER=NO WITH_3DMAPPER=NO qmake -qt=qt5 ../src/mudlet.pro
 +
 
 +
[[File:After-qmake.png|center|thumb|After qmake]]
 +
 
 +
''' THEN: '''
 +
:For the fastest compile time while still being able to use the system at all (~35min on a RPi4 with 4GB of ram)
 +
make -j $(expr `nproc` - 1)
 +
 
 +
''' OR: '''
 +
 
 +
:Use this if you have an older Raspberry Pi. Be prepared for it to take a while (over an hour) - ''it is not recommended to try to more than one compilation task at a time on the older systems with the '''-j''' option as they will only have a system memory with enough space for one of some of those tasks'':
 +
make
 +
 
 +
[[File:Success.png|center|thumb|Success!]]
 +
 
 +
''' 4. Install the application you have just compiled '''
 +
 
 +
sudo make install
 +
 
 +
[[File:Installed.png|center|thumb|Installed now]]
 +
 
 +
''' 5. Enjoy! '''
 +
 
 +
# mudlet is in the path, can just run it
 +
mudlet
 +
 
 +
== Compiling on Arch Linux ==
 +
 
 +
===AUR Install and Compile===
 +
Mudlet is available in the [https://aur.archlinux.org Arch User Repository].
 +
(If the AUR has become unmaintained/orphaned, then skip below to [https://wiki.mudlet.org/w/Compiling_Mudlet#Manual_Install_and_Compile Manual install].)
 +
 
 +
To install it use your favourite AUR helper (helper tool will automatically resove dependancies); example using ''yay'' :
 +
yay -S mudlet
 +
 
 +
For more info on this process, visit [https://wiki.archlinux.org/index.php/Arch_User_Repository Arch User Repository - ArchWiki].
 +
 
 +
''Note: For the most recent development version of Mudlet, replace 'mudlet' with 'mudlet-git' in the above commands and proceed as described.''
 +
 
 +
''Built in fonts have been disabled, but are available in packages listed as optional dependancies.''
 +
 
 +
''Discord support in Mudlet depends on an external library provided by discord-rpc-api, which is also available in AUR, choose whichever variant suits you best.''
 +
 
 +
===Manual Install and Compile===
 +
These instructions will get you setup compiling on Arch. Need a hand? Join us on Mudlet's [https://discord.gg/BwgJpMj Discord] or [http://forums.mudlet.org/viewforum.php?f=7 forums].
 +
 
 +
'''1. necessary dependencies'''
 +
 
 +
Majority of required dependencies can be obtained from repositories, and can be installed with following command:
 +
 
 +
  sudo pacman -S --needed cmake qt5-multimedia hunspell libzip lua51-filesystem qt5-gamepad lua51-luautf8 pugixml \
 +
  ttf-font qtkeychain-qt5 boost qt5-tools ttf-bitstream-vera ttf-ubuntu-font-family noto-fonts-emoji glu luarocks
 +
 
 +
Few of required Lua modules are not available in official repositories, so they have to be installed using ''luarocks''
 +
  sudo lua5.1 /usr/bin/luarocks install lcf
 +
  sudo lua5.1 /usr/bin/luarocks install luautf8
 +
  sudo lua5.1 /usr/bin/luarocks install lua-yajl
 +
  sudo lua5.1 /usr/bin/luarocks install lrexlib-pcre
 +
  sudo lua5.1 /usr/bin/luarocks install luasql-sqlite3
 +
  sudo lua5.1 /usr/bin/luarocks install lua-zip
 +
 
 +
There is an optional dependency for discord integration:
 +
  git clone https://github.com/discord/discord-rpc
 +
  cd discord-rpc
 +
  mkdir build
 +
  cd build
 +
  cmake .. -DCMAKE_INSTALL_PREFIX=/usr
 +
  sudo cmake --build . --config Release --target install
 +
 
 +
'''2. obtaining the source code'''
 +
 
 +
Obtain the latest in-development code with:
 +
  git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 +
  mkdir Mudlet/build
 +
  cd Mudlet/build
  
$ tar -xvzf libzip-0.11.1.tar.gz && cd libzip-0.11.1
+
'''3. compiling the code'''
  
$ ./configure && make && sudo make install
+
There below are two ways to build with qmake, the first is for general use, the second is for developers:
 +
  qmake ../src/mudlet.pro
 +
'''*OR*'''
 +
  qmake CONFIG+=debug ../src/mudlet.pro
  
 +
'''Now finish compiling:'''
 +
  make -j `nproc`
  
'''4. Build Mudlet.'''
+
'''4. installing compiled code'''
  
$ cd .. && qmake && make
+
After successful code compilation, next few commands will install resulting binaries, desktop file for menus and appropriate icon.
 +
  sudo make install
 +
  sudo cp ../mudlet.png /usr/share/pixmaps
 +
  sudo cp ../mudlet.desktop /usr/share/applications
  
 +
'''5. optional additional software'''
  
 +
One of the major reasons for compiling Mudlet from source is the ability to unlock more features that are not enabled in official AppImage.
 +
Manual compilation will resolve the issues with sound by using system provided libraries, as well as enable more detailed theming of Mudlet application itself.
 +
However, do take note that Mudlet is a Qt based program, and that theming will not 'just work' in GTK based desktop environments (Gnome, XFCE, MATE, Budgie).
 +
  sudo pacman -S install qt5ct
 +
will install a tool for configuration of look and feel of Qt programs inside those desktop environments.↵Users of Qt based Desktop environments (KDE Plasma, LXQT) can simply use settings provided by environment itself.
  
== Compiling in ArchLinux ==
+
Many of Qt widget styles and color schemes are available in official repositories, and will make Mudlet better.
  
The best way to do this would be to use the PKGBUILD found [https://aur.archlinux.org/packages.php?ID=51661 here]. You'll just download the PKGBUILD into a directory, run
+
6. '''Mudlet on Wayland'''
  
makepkg
+
Mudlet compiled like this will run and work on Wayland, however, there are a few quirks with Keybindings (Numpad may not work as expected).
sudo pacman -U [name of the generated pkg file]
+
Until that is resolved you may wish to start mudlet with:
 +
  QT_QPA_PLATFORM=xcb mudlet
 +
(enter in terminal or simply change the Exec= line in /usr/share/applications/mudlet.desktop)
  
and you'll be done. For more info on what this does, visit [https://wiki.archlinux.org/index.php/Arch_User_Repository this site]. If you really want to compile it by hand, please note that it won't be as simple due to ArchLinux' aggressive update philosophy. The instructions provided here might be outdated due to said philosophy, so you will have to know how to use [http://www.google.com Google], and you'll need to be willing to read through C++ compilation errors. If you're still willing to go through this, then read on.
+
7. '''uninstallation'''
  
'''1. Install required packages'''
+
You can reverse the process described in this guide with following command:
  
Mudlet has a bunch of dependencies that you'll need to compile the source. You can get an updated list of packages [http://packages.debian.org/sid/mudlet here], it's just a matter of figuring out what they're called in pacman. As for the lua dependencies, I recommend you get luarocks, and use it to install them. You'll also need git to download the source.
+
  sudo rm -fr /usr/bin/mudlet /usr/share/mudlet /usr/share/applications/mudlet.desktop /usr/share/pixmaps/mudlet.png
  
'''2. Get the source through Git'''
+
== Compiling on Fedora (aarch64) ==
  
Run the following in a terminal to get the source:
+
'''1.  Install dependencies'''
 +
sudo dnf groupinstall "Development Tools" "Development Libraries"
  
  git clone git://git.code.sf.net/p/mudlet/code
+
  sudo dnf install compat-lua compat-lua-devel compat-lua-libs hunspell-devel lua5.1-filesystem luarocks pugixml-devel qtkeychain-qt5-devel bitstream-vera-fonts-all ccache qt-creator qt5-qtmultimedia-devel qt5-qtgamepad-devel yajl-devel qtchooser qt5-qttools-devel qt5-qttools-static zziplib-devel pcre-devel libzip-devel sqlite-devel
{old location git://mudlet.git.sourceforge.net/gitroot/mudlet/mudlet no longer valid}
 
  
it should download the source automatically.
+
sudo luarocks --lua-version 5.1 --tree=/usr install luazip
 +
sudo luarocks --lua-version 5.1 --tree=/usr install luasql-sqlite3
 +
sudo luarocks --lua-version 5.1 --tree=/usr install lcf
 +
sudo luarocks --lua-version 5.1 --tree=/usr install luautf8
 +
sudo luarocks --lua-version 5.1 --tree=/usr install lua-yajl
 +
sudo luarocks --lua-version 5.1 --tree=/usr install lrexlib-pcre
 +
In your user's home directory:
  
'''3. Address yajl issue'''
+
If you use a bash shell:
 +
luarocks --lua-version 5.1 path --no-bin >> .bashenv
 +
source .bashenv
 +
If you use a zsh shell:
 +
luarocks --lua-version 5.1 path --no-bin >> .zshenv
 +
source .zshenv
 +
If you use a csh shell:
 +
luarocks --lua-version 5.1 path --no-bin >> .cshenv
 +
source .cshenv
 +
This should cover paths, but you may want to reboot to be sure.
  
There are two versions of yajl: 1 and 2. If you installed yajl via pacman, you probably have 2. If you do have two, then you'll have to download [http://vrac.kadarniad.fr/lua_yajl2.c this file] and add it into the src directory. If you do not want to do this, then download and install yajl1 from AUR.
+
'''2. Obtain the source code'''
 +
git clone --recursive --branch=development <nowiki>https://github.com/Mudlet/Mudlet.git</nowiki>
 +
mkdir Mudlet/build
 +
cd Mudlet/src
  
'''3. Edit src.pro''' (to be improved)
+
'''3. Make necessary compiling instruction adjustments'''
  
Run the following in a terminal from the src directory:
+
Edit mudlet.pro - find these lines in mudlet.pro and make the following changes:
for i in *.{cpp,h} ; do sed -i 's/#include <phonon>/#include <phonon\/MediaObject>\n#include <phonon\/AudioOutput>/' $i ; done
+
     linux {
sed -i 's/lua_yajl1.c/lua_yajl2.c/' TLuaInterpreter.cpp
+
         LIBS += \
sed -i 's/-lhunspell/-lhunspell-1.3/' src.pro
+
             -llua5.1 \
sed -i 's/lua_yajl1.c/lua_yajl2.c/' src.pro
+
             -lhunspell
sed -i '/MOC_DIR.*/i QMAKE_MOC += -DBOOST_TT_HAS_OPERATOR_HPP_INCLUDED' src.pro
+
         INCLUDEPATH += /usr/include/lua5.1
sed -i '/.*unix:LIBS.*/a -lz \\' src.pro
+
     }
sed -i 's#QString path = \"mudlet-lua/lua/LuaGlobal.lua\";#QString path = \"/usr/local/share/mudlet/LuaGlobal.lua\";#' TLuaInterpreter.cpp
+
We're adding a - between lua and 5.1 and adding -1.7 to hunspell under LIBS so that it becomes this:
 +
     linux {
 +
         LIBS += \
 +
             -llua-5.1 \
 +
             -lhunspell-1.7
 +
         INCLUDEPATH += /usr/include/lua5.1
 +
     }
 +
Save and exit.
  
'''4. Compile the source'''
+
'''4. Compile'''
 +
cd ../build
 +
Run this in the build directory:
 +
WITH_FONTS=NO WITH_OWN_QTKEYCHAIN=NO WITH_UPDATER=NO WITH_VARIABLE_SPLASH_SCREEN=NO XDG_DATA_DIRS=/usr/share qmake-qt5 PREFIX=/usr INCLUDEPATH+=/usr/include/lua-5.1 LUA_SEARCH_OUT=lua-5.1 ../src/mudlet.pro
 +
An explanation of the qmake arguments -- we're passing these environment variables to mudlet.pro:
 +
WITH_FONTS=NO WITH_OWN_KEYCHAIN=NO WITH_UPDATER=NO WITH_VARIABLE_SPLASH_SCREEN=NO XDG_DATA_DIRS=/usr/share
 +
Adding build variables to mudlet.pro so that it finds the correct libraries:
 +
PREFIX=/usr INCLUDEPATH+=/usr/include/lua-5.1
 +
And finally adding a build variable to translations/translated/updateqm.pri so that it uses the correct version of the Lua compiler (Fedora also comes with 5.4) to generate translation statistics.
 +
LUA_SEARCH_OUT=lua-5.1
 +
Once complete, run the following:
  
qmake
+
If you have time to kill (About 10 minutes on an Apple M1 Max in Fedora):
 
  make
 
  make
 +
If you want it done as fast as possible(Less than a minute on an Apple M1 Max in Fedora):
 +
make -j `nproc`
 +
Or if you want something in between, make -j `nproc` tells it to use all available processor cores.  If you want to use a specific number instead (ie 2), you can use:
 +
make -j 2
 +
 +
'''5. Install'''
 +
sudo make install
 +
sudo cp ../mudlet.png /usr/share/pixmaps
 +
sudo cp ../mudlet.desktop /usr/share/applications
 +
 +
'''6. Hang onto the cloned git repo '''
 +
If you need to uninstall, you can go back into the /build directory and 'sudo make uninstall'.
 +
 +
== Compiling on Gentoo ==
 +
An [https://github.com/toaster/gentoo-overlay overlay containing Mudlet is available] for compiling Mudlet on Gentoo.
 +
 +
== Compiling on Windows ==
 +
 +
* Install '''MSYS2''': https://www.msys2.org
 +
 +
* At the end of installation uncheck '''run msys2 now''' and click '''finish'''
 +
 +
* Run '''MSYS2 MINGW64''' from the start menu
 +
 +
* Run the following in the opened MSYS2 terminal (you right-click in order to paste):
 +
pacman --files --refresh
 +
pacman --sync git mingw-w64-x86_64-qt-creator mingw-w64-x86_64-cmake mingw-w64-x86_64-ninja mingw-w64-x86_64-clang-libs --noconfirm
 +
 +
* Run the following from the MSYS2 terminal:
 +
git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 +
 +
* Setup the development environment (~5-10min) by running:
 +
./Mudlet/CI/setup-windows-sdk.sh
 +
 +
Take note of the message at the end to add the variables to your environment once you have opened the project in Qt Creator.
 +
(WITH_MAIN_BUILD_SYSTEM, MINGW_BASE_DIR, LUA_PATH, LUA_CPATH)
 +
[[File:Windows environment variables.png|500px|center]]
 +
 +
{{note}} This might not work on windows arm64, pacman freezes.
 +
 +
* Open Qt Creator. You will need to open it via MSYS2 every time:
 +
/mingw64/bin/qtcreator.exe
 +
 +
* Press '''link with Qt''' on the bottom right of Qt Creator
 +
 +
[[File:Link with qt.png|500px|center]]
 +
 +
* Choose <code>C:/msys64/mingw64</code> as the location then restart Qt Creator
 +
 +
[[File:Qt location.png|500px|center]]
 +
 +
* '''Open project'''; C:/msys64/home/<user>/Mudlet/src/mudlet.pro
 +
 +
[[File:Open new project - qtcreator.png|500px|center]]
 +
 +
* In Build Environment details, set environment variables to what was stated in the sdk-setup script above.
 +
 +
[[File:Build environmental variables.png|500px|center]]
 +
 +
* Build Mudlet (Ctrl+B)
 +
* Run Mudlet (Ctrl+R)
 +
 +
 +
=== Contributing changes ===
 +
 +
Once you're all done with your changes, contribute them to Mudlet using a [https://help.github.com/desktop/guides/contributing-to-projects/creating-a-pull-request/#platform-windows pull request]. Thanks for improving open-source!
 +
 +
== Compiling on Github Codespaces ==
 +
 +
[https://github.com/features/codespaces/ Github Codespaces] allow you to code and run Mudlet all from the browser - makes it a lot easier to get started. It also allows you to code Mudlet itself from any computer in the world!
 +
 +
'''1. Create a new codespace'''
 +
 +
Create a new Codespace by going to https://github.com/Mudlet/Mudlet using Google Chrome or Microsoft Edge (Firefox at the time of the writing doesn't have working copy/paste). There, click the green "Code" button, select the "Codespaces" tab and click "New codespace".
 +
 +
[[File:New codespace.png|alt=New codespace screenshot|frameless]]
 +
 +
'''2. Wait for it to load'''
 +
 +
This will take a while (~5min) so grab a tea:
 +
 +
[[File:Building Visual Studio Codespace.png|frameless]]
 +
 +
'''3. Connect to the environment'''
 +
 +
Go to the <code>Ports</code> section at the bottom and change the Port Privacy of the Open Mudlet port to Public:
 +
 +
[[File:Port privacy in Github Codespaces.png|900x900px]]
 +
 +
 +
Then connect to your online Linux desktop with <code>mudlet</code> as the password by clicking on the web icon.
 +
 +
[[File:Connect to remote machine.png|frameless]]
 +
 +
 +
In case it can't connect, make sure the port privacy is set to <code>Public</code>. If it still can't connect, try 4-5 more times - eventually it'll work.
 +
 +
 +
 +
We chose a retro 90's look here to fit with the whole hacking theme, so if you see this you're good 😉
 +
 +
[[File:Github_codespaces_desktop.png|alt=|frameless|400x400px]]
 +
 +
'''4. Build Mudlet'''
 +
 +
In Codespaces, hit <code>F7</code> and select <code>Let CMake guess...</code>
 +
 +
[[File:CMake configuration.png|none]]
 +
 +
It will then start building Mudlet automatically. Using the [https://docs.github.com/en/free-pro-team@latest/github/developing-online-with-codespaces/about-billing-for-codespaces Basic instance] (only kind available in beta) the first-time build will take ~25min, so take a break here - you've made excellent progress. All follow-up compiles after this will be quicker, by the way.
 +
 +
[[File:Building Mudlet in codespaces.png|none]]
  
 
'''5. Run Mudlet'''
 
'''5. Run Mudlet'''
  
  ./mudlet
+
[[File:Launch Mudlet.png|none]]
 +
 
 +
Hit the little play button at the bottom of the screen, and Mudlet will now launch in the remote connection tab. Not working? [https://discord.gg/kuYvMQ9 We can help]. Otherwise, enjoy!
 +
 
 +
[[File:Mudlet running remotely.png ‎|500px]]
 +
 
 +
Note: When the codespace is unused for a while, it will disconnect. It'll never disconnect while you're actively using it. See [https://github.com/microsoft/vscode-dev-containers/issues/588 Github issue] for details.
 +
 
 +
== Developing with Docker ==
 +
 
 +
Docker is a system designed for more reproducible and isolated builds. A docker setup exists and has been tested using Pop OS! 20.04 (which is derived from Ubuntu 20.04). First, follow the instructions to install both [https://docs.docker.com/get-docker/ docker] and [https://docs.docker.com/compose/install/ docker-compose].
 +
 
 +
Clone the development branch
 +
 
 +
  git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 +
  cd Mudlet/docker
 +
 
 +
Make a local copy of the .env.template file:
 +
 
 +
  cp .env.template .env
 +
 
 +
If you wish to customize things like the number of cores to use for building mudlet, feel free to change the corresponding values in the .env file.
 +
 
 +
To run Qt-Creator and develop Mudlet, run <code>docker-compose up dev</code>.
 +
 
 +
To run Mudlet, run <code>docker-compose up mudlet</code>. Note: At the moment, the mudlet build will not persist settings past container rebuilds.
 +
 
 +
= Setting up IDEs =
 +
== CLion ==
 +
=== Qt not detected ===
 +
If you'd like to use CLion and it is giving the following error:
 +
 
 +
<nowiki>
 +
    By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
 +
    asked CMake to find a package configuration file provided by "Qt5Core", but
 +
    CMake did not find one.
  
== Compiling in Gentoo ==
+
    ...
An [https://github.com/toaster/gentoo-mudlet-overlay overlay is available] for compiling Mudlet on Gentoo.
+
  </nowiki>
  
== Compiling on Windows 7 ==
+
You can fix this by setting <code>-DCMAKE_PREFIX_PATH=<your Qt + version + compiler location></code>. For example: <code>-DCMAKE_PREFIX_PATH=/media/vadi/SSDer/Programs/Qt/5.14.2/gcc_64/</code> [[File:CLion CMake settings - finidng Qt.png|700px|none]]
  
'''1.Download & Install the Prerequisites'''
+
=== CLion setup on Windows ===
 +
After running <code>setup-windows-sdk.ps1</code> make sure to set Cmake options to:
 +
-DCMAKE_PREFIX_PATH=C:\Qt\Tools\mingw730_32;C:\Qt\5.14.2\mingw73_32 -DBoost_INCLUDE_DIR=C:\Libraries\boost_1_77_0
 +
''Directories might vary slightly, when different Qt, Boost or MinGW version will be used.''
  
Qt 5.2
+
[[File:Clion Settings - Cmake.png|frameless|700x700px]]
  http://qt-project.org/downloads
 
In this tutorial, it is installed in C:\Qt\ (so you will have C:\Qt\5.x.x)
 
Mingw-builds:
 
  http://sourceforge.net/projects/mingwbuilds/files/host-windows/releases/4.8.1/32-bit/threads-posix/dwarf/
 
extract this to C:\mingw32
 
latest msys from:
 
  http://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/
 
put the msys folder in C:\mingw32
 
  
  
'''2.Download libraries in MSYS'''
 
  
Open MSYS(click msys.bat in the msys folder), where you'll be in a home directory. Now enter:
+
You will need 32 bit version of MinGW. Set it in the <code>Toolset</code> field to:
 +
  C:\Qt\Tools\mingw730_32
  
mkdir src
+
''Directory may be slightly different if MinGW version used will change.''
cd src
 
wget http://downloads.sourceforge.net/hunspell/hunspell-1.3.2.tar.gz
 
wget http://www.lua.org/ftp/lua-5.1.5.tar.gz
 
wget ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/pcre-8.33.tar.gz
 
wget http://zlib.net/zlib-1.2.8.tar.gz
 
wget http://www.sqlite.org/2013/sqlite-autoconf-3071700.tar.gz
 
  
You'll need to manually download and extract the contents of these files into your msys src folder as well.
+
[[File:Toolchain.png|frameless|700x700px]]
The path for msys src is C:\mingw32\msys\home\your_name\src\.
 
  
Boost:
+
=== Clang Tidy ===
  http://sourceforge.net/projects/boost/files/boost/1.45.0/boost_1_45_0.tar.gz/download, extract the "boost" folder to C:/mingw32/include/
+
Ensure that CLion is set to run the project's [https://www.jetbrains.com/help/clion/clang-tidy-checks-support.html#paticularcheck .clang-tidy checks] with the <code>Prefer .clang-tidy files over IDE settings</code> option:
Yajl:
 
  http://github.com/lloyd/yajl/tarball/2.0.1, put it into the msys src folder
 
  
Now untar/unzip everything into the src folder.
+
[[File:Clang Tidy CLIon.png|700px|none]]
  
Syntax inside msys for untarring: tar -zxvf hunspell-1.3.2.tar.gz
+
This helps us catch any issues just a bit earlier.
and so on for the rest
 
  
'''3.Compiling libraries'''
+
===Checking memory leaks & other issues (sanitizers)===
 +
Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:
  
''''MSYS Compilations''''
+
* [https://clang.llvm.org/docs/LeakSanitizer.html LeakSanitizer] for detecting memory leaks
 +
* [https://clang.llvm.org/docs/AddressSanitizer.html AddressSanitizer] for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
 +
* [https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html UndefinedBehaviourSanitizer] for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
 +
* [https://clang.llvm.org/docs/MemorySanitizer.html MemorySanitizer] for detecting reading uninitialised memory
 +
* [https://clang.llvm.org/docs/ThreadSanitizer.html ThreadSanitizer] for detecting threading issues
  
All these will be compiled inside the msys command prompt
+
To use the sanitisers, set the <code>USE_SANITIZER</code> CMake variable to one or several variables (separate by comma): <code>Address</code>, <code>Memory</code>, <code>MemoryWithOrigins</code>, <code>Undefined</code>, <code>Thread</code>, or <code>Leak</code>
cd into each respective directory:
 
  
Hunspell:
+
To use them in CLion, adjust the CMake settings:
./configure --prefix=/c/mingw32
 
You'll get an error in localname.c if you make right away, edit this file (intl/localename.c, comment out case SUBLANG_SINDHI_PAKISTAN: return "sd_PK";)
 
make && make install
 
  
YAJL:
+
[[File:Clion_cmake_settings.png|frameless|890x890px]]
Edit CMakeLists.txt in the base dir of YAJL, remove all the windows specific compiler garbage:
+
 
SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /W4") to SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS}")
+
Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.
SET(linkFlags "/PDB:NONE /INCREMENTAL:NO /OPT:NOREF /OPT:NOICF") to SET(linkFlags)
+
 
SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} /wd4996 /wd4255 /wd4130 /wd4100 /wd4711") to SET(CMAKE_C_FLAGS "${CMAKE_C_FLAGS}")
+
=== Clang Format ===
SET(CMAKE_C_FLAGS_DEBUG "/D DEBUG /Od /Z7") to SET(CMAKE_C_FLAGS_DEBUG "-g")
+
Ensure that [https://www.jetbrains.com/help/clion/clangformat-as-alternative-formatter.html#clion-support CLion is set to use] the <code>.clang-format</code> formatting style:
SET(CMAKE_C_FLAGS_RELEASE "/D NDEBUG /O2") to SET(CMAKE_C_FLAGS_RELEASE "-O2")
+
 
mkdir build
+
[[File:Clang-format CLion.png]]
cmake -G "MSYS Makefiles" ..
+
 
make
+
This helps keep the look'n'feel of the source code in a consistent manner, even with many people contributing to Mudlet.
cp yajl-2.0.1/lib/* /c/mingw32/lib/
+
 
cp -R yajl-2.0.1/include/* /c/mingw32/include/
+
== Visual Studio Code ==
+
 
Lua:
+
To set the path in Visual Studio Code, open settings, search for <code>cmake environment</code> and set the <code>CMAKE_PREFIX_PATH</code> to your path, such as <code>/home/vadi/Programs/Qt/5.15.2/gcc_64</code>:
edit the Makefile, change INSTALL_TOP= /usr/local to INSTALL_TOP= /c/mingw32
+
 
  make mingw
+
[[File:CMake path in Visual Studio Code.png|none]]
  make install
+
 
   
+
===Clang Tidy===
  PCRE:
+
clang-tidy catches common programming issues, run it by selecting 'Analysis' from the command palette (Ctrl+Shift+P by default):
./configure --prefix=/c/mingw32 && make && make install
+
 
+
[[File:Clang-tidy in vscode.png|none]]
Sqlite:
+
 
./configure --prefix=/c/mingw32 && make && make install
+
It is also possible [https://devblogs.microsoft.com/cppblog/visual-studio-code-c-december-2021-update-clang-tidy/ check status of analysis and cancel if needed].
    
+
 
ZLib:
+
===Checking memory leaks & other issues (sanitizers)===
make -f win32/Makefile.gcc
+
Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:
export INCLUDE_PATH=/c/mingw32/include
+
 
export LIBRARY_PATH=/c/mingw32/lib
+
* [https://clang.llvm.org/docs/LeakSanitizer.html LeakSanitizer] for detecting memory leaks
export BINARY_PATH=/c/mingw32/bin
+
* [https://clang.llvm.org/docs/AddressSanitizer.html AddressSanitizer] for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
  make -f win32/Makefile.gcc install  
+
* [https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html UndefinedBehaviourSanitizer] for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
 +
* [https://clang.llvm.org/docs/MemorySanitizer.html MemorySanitizer] for detecting reading uninitialised memory
 +
* [https://clang.llvm.org/docs/ThreadSanitizer.html ThreadSanitizer] for detecting threading issues
 +
 
 +
To use the sanitisers, set the <code>USE_SANITIZER</code> CMake variable to one or several variables (separate by comma): <code>Address</code>, <code>Memory</code>, <code>MemoryWithOrigins</code>, <code>Undefined</code>, <code>Thread</code>, or <code>Leak</code>
 +
 
 +
To use them in VSCode, set the <code>cmake.configureSettings</code> variable:
 +
 
 +
[[File:Cmake.configureSettings option in vscode.png|frameless|890x890px]]
 +
 
 +
[[File:Choosing which sanitizers in vscode to use.png|frameless|891x891px]]
 +
 
 +
Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.
 +
 
 +
== Qt Creator==
 +
===Clang Tidy and Clazy===
 +
 
 +
Configure Mudlet-specific checks for [https://clang.llvm.org/extra/clang-tidy/ clang-tidy] and [https://github.com/KDE/clazy clazy] tools help catch any issues early on. See  [https://doc.qt.io/qtcreator/creator-clang-tools.html Qt Creator's instructions] for setting this up - clang-tidy can use the <code>.clang-tidy</code> file that's available at the root of the repository, and for clazy enable <code>level0</code> and <code>level1</code> checks.
 +
 
 +
[[File:Clang tidy configuration.png|frame|none]]
 +
[[File:Clazy configuration.png|frame|none]]
 +
 
 +
===Checking memory leaks & other issues (sanitizers)===
 +
Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:
 +
 
 +
* [https://clang.llvm.org/docs/LeakSanitizer.html LeakSanitizer] for detecting memory leaks
 +
* [https://clang.llvm.org/docs/AddressSanitizer.html AddressSanitizer] for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
 +
* [https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html UndefinedBehaviourSanitizer] for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
 +
* [https://clang.llvm.org/docs/MemorySanitizer.html MemorySanitizer] for detecting reading uninitialised memory
 +
* [https://clang.llvm.org/docs/ThreadSanitizer.html ThreadSanitizer] for detecting threading issues
 +
 
 +
To use the sanitisers, set the <code>USE_SANITIZER</code> CMake variable to one or several variables (separate by comma): <code>Address</code>, <code>Memory</code>, <code>MemoryWithOrigins</code>, <code>Undefined</code>, <code>Thread</code>, or <code>Leak</code>
 +
 
 +
To use them in Qt creator, head to <code>Projects</code> - <code>Build</code>:
 +
 
 +
[[File:Sanitisers in qt creator.png|frameless|890x890px]]
 +
 
 +
Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.
 +
 
 +
==Clang Format==
 +
Ensure that Qt Creator is set to use the <code>.clang-format</code> formatting style in the C++ settings. Turn on <code>Format instead of indenting</code> for <code>Ctrl+I</code> to format code, and ensure <code>Override Clang Format configuration file</code> is disabled:
 +
 
 +
[[File:Qt Creator clang format.png]]
 +
 
 +
This helps keep the look'n'feel of the source code in a consistent manner, even with many people contributing to Mudlet.
 +
 
 +
=Building with multiple versions of Lua=
 +
Mudlet uses Lua 5.1 only, so if you are compiling on a system that also has later versions installed, you might get the following error: <code>‘LUA_GLOBALSINDEX’ was not declared in this scope</code>.
 +
 
 +
To fix this, pass the path to Lua headers explicitly. For CMake: <code>-DLUA_INCLUDE_DIR=/usr/include/lua5.1</code> (adjust as needed).
 +
 
 +
= Key contributing information =
 +
 
 +
Clang format is used to automatically format code submissions using the [https://github.com/Mudlet/Mudlet/blob/development/src/.clang-format src/.clang-format] style. [http://doc.qt.io/qtcreator/creator-beautifier.html See here] how to enable clang-format with Qt Creator - and make sure to specify the 'File' option for the configuration style.
 +
 
 +
Branches:
 +
 
 +
'''development''' is the development branch where new features can go.
 +
 
 +
Workflow:
 +
 
 +
Fork and submit a PR with your changes ([https://guides.github.com/activities/forking/ Github tutorial]).
 +
 
 +
Here is a list of package versions delivered with different Linux distros. You may want to upgrade these:
 +
https://repology.org/project/mudlet/versions
 +
 
 +
= Lua & Luarocks =
 +
 
 +
Mudlet includes a [https://en.wikipedia.org/wiki/Lua_(programming_language) Lua] (version 5.1) scripting system for the end-user, which you, as a reader of this Wiki, may already be aware of! If not, you might wish to (after you have got your hands on a working Mudlet) take a look at [https://wiki.mudlet.org/w/Manual:Lua_Functions Mudlet Lua API] as that is the recommended place to find out the details of all the functions that Mudlet provides on top of the core Lua functionality.
 +
 
 +
Some of that ability comes from extra code that is not built-in to Lua but is in the form of external modules either in the form of script (text) files written in the Lua language itself or binary (library) files compiled from (usually but not exclusively [https://en.wikipedia.org/wiki/C_(programming_language) 'C']) source code. In order to have that functionality Mudlet makes use of several of these modules which can most readily (if not already available as "packages" for a particular Operating System) be obtained as '''rocks''' from the public [https://en.wikipedia.org/wiki/LuaRocks Luarocks] collection. Such a rock actually consists of a ''rockspec'' file that gives instructions to the Luarocks tool how to obtains the (source) code, compile it on any supported OS into the form that a Lua interpreter (including the one included in '''''each''''' running Mudlet ''profile'') can use, and where and what it will be placed and called when it has been made. After that it should be available to Lua via the ''require'' command.
 +
 
 +
Anyone compiling Mudlet for themselves will find it desirable to ensure they have a usable Luarocks installation and have the ''lua-yajl'' module installed before commencing to compile Mudlet itself; this is because a Lua (version 5.1) interpreter and that module are used within the build process of making the executable code that is the Mudlet application.
 +
 
 +
== Included Modules ==
 +
 
 +
# [https://luarocks.org/modules/xavier-wang/luautf8 luautf8] (manual in README)
 +
# [https://luarocks.org/modules/martin-eden/lcf lcf] (customised version)
 +
# [https://luarocks.org/modules/hisham/luafilesystem luafilesystem] ([http://lunarmodules.github.io/luafilesystem/manual.html manual])
 +
# [https://luarocks.org/modules/rrt/lrexlib-pcre lrexlib-pcre] ([https://rrthomas.github.io/lrexlib/manual.html manual])
 +
# [http://lunarmodules.github.io/luasql/ luasql-sqlite3] (http://lunarmodules.github.io/luasql/manual.html manual)
 +
# [https://luarocks.org/modules/brimworks/lua-yajl lua-yajl] (manual in README)
 +
# [https://luarocks.org/modules/mpeterv/luazip luazip] ([http://mpeterv.github.io/luazip/ manual])
 +
 
 +
== Adding Luarocks ==
 +
 
 +
Here's a rundown on checking you can use luarocks. Here we will use the bit32 module as an example.
 +
 
 +
 
 +
1. Install via luarocks
 +
 
 +
  > luarocks install bit32
 +
 
 +
2. Check where luarocks installs the modules.  Note the modules section.
 +
 
 +
  <nowiki>
 +
> luarocks show bit32
 +
 
 +
bit32 5.3.5.1-1 - Lua 5.2 bit manipulation library
 +
 
 +
bit32 is the native Lua 5.2 bit manipulation library, in the version from Lua 5.3; it is compatible with Lua 5.1, 5.2, 5.3 and 5.4.
 +
 
 +
License:       MIT
 +
Homepage:      http://www.lua.org/manual/5.2/manual.html#6.7
 +
Installed in:   /usr/local
 +
 
 +
Modules:
 +
        bit32 (/usr/local/lib/lua/5.1/bit32.so)
 +
 
 +
Depends on:
 +
        lua >= 5.1, < 5.5 (using 5.1-1)
 +
</nowiki>
 +
 
 +
3. Recompile mudlet. You may need to adjust lua path and cpath information for your environmentYou can use the following commands to help find this information.
  
'''3.Downloading Mudlet Sources'''
+
<nowiki>
 +
> luarocks --lua-version 5.1 path --no-bin
 +
export LUA_PATH='./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;/home/username/.luarocks/share/lua/5.1/?.lua;/home/username/.luarocks/share/lua/5.1/?/init.lua'
 +
export LUA_CPATH='./?.so;/usr/local/lib/lua/5.1/?.so;/usr/lib/x86_64-linux-gnu/lua/5.1/?.so;/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;/home/username/.luarocks/lib/lua/5.1/?.so
 +
</nowiki>
  
From within msys:
+
Or from within mudlet itself you can issue these commands to double check the correct paths are being used.
  
cd to wherever you want to put your sources. You can do this from something like C:\gits\
+
<nowiki>
 +
> lua print(package.path)
 +
/home/username/.config/mudlet/profiles/localhost/?.lua;/home/zooka/.config/mudlet/profiles/localhost/?/init.lua;./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;/home/username/.luarocks/share/lua/5.1/?.lua;/home/username/.luarocks/share/lua/5.1/?/init.lua
 +
 
 +
> lua print(package.cpath)
 +
/home/username/.config/mudlet/profiles/localhost/?.so;/home/username/Workspace/mudlet-dev/Mudlet/build/lib/?.so;./?.so;/usr/local/lib/lua/5.1/?.so;/usr/lib/x86_64-linux-gnu/lua/5.1/?.so;/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;/home/username/.luarocks/lib/lua/5.1/?.so
 +
</nowiki>
  
git clone https://github.com/Chris7/Mudlet2.git
+
4. Recompile and run a test script using the [https://www.lua.org/pil/8.1.html require command] to load in the necessary library.
cd Mudlet2/src (if using my github repo)
 
edit src.pro
 
add to win32:INCLUDEPATH
 
    "c:\mingw32\include"
 
add  to win32:LIBS:
 
    "c:\mingw32\lib" \
 
-lzlib1
 
qmake.exe
 
make
 
  
'''4.Copy Needed DLLs'''
+
<nowiki>
 +
bit32 = require("bit32")
  
copy the following dll's into the release directory:
+
function bit32_test()
 +
  bit32.band(0,1)
 +
end
 +
</nowiki>
  
From Qt\5.x.x\mingw42_32\bin:
+
= Enabling Debug Build =
icudt51.dll, icuin51.dll, icuuc51.dll, Qt5Core.dll, Qt5Gui.dll, Qt5Network.dll, Qt5OpenGL.dll, Qt5Widgets.dll
 
copy mudlet-lua into the release directory
 
  
'''5.Setting up Lua libraries'''
+
To enable a debug build that can be run through GDB:
At this point your lua install will be bare-bones. You'll need to install lua packages:
 
  
Get the 32 bit of luarocks, install it with install.bat /p C:\LuaRocks /MW
+
* follow all steps until qmake
edit C:\LuaRocks\2.0\lua\luarocks\cfg.lua, change mingw32-gcc to gcc
+
* modify the qmake line by adding in debug info, e.g.:
 +
  qmake CONFIG+=debug ../src/mudlet.pro
 +
* compile as normal
 +
* attach gdb to mudlet
 +
  gdb ./mudlet
 +
* within gdb command line start mudlet running by:
 +
  run
 +
* proceed to crash mudlet then type
 +
  bt
 +
* submit the output with your bug reports.
  
From windows command line:
+
= Compile Time Flags =
go into C:\LuaRocks\2.0
 
luarocks install LuaFileSystem
 
luarocks install LuaZip
 
luarocks install LuaSQL-SQLite3 SQLITE_INCDIR="c:\mingw32\include"
 
luarocks install lrexlib-sqlite PCRE_LIBDIR="c:\mingw32\lib" PCRE_INCDIR="c:\mingw32\include"
 
  
Now copy the contents of from LuaRocks/lib/lua/5.1 to the mudlet release directory
+
<nowiki>
 +
DEBUG_UTF8_PROCESSING - for decoding the UTF-8 (1 byte with the MSB set or 2, 3 or 4 bytes) encoding
 +
DEBUG_GB_PROCESSING - for decoding the GBK (2 bytes) or GB18030 (2 or 4 bytes) encodiing
 +
DEBUG_BIG5_PROCESSING - for decoding the Big5-ETEN or Big5-HKSCS encodings
 +
DEBUG_EUC_KR_PROCESSING - for decoding the EUC_KR encoding
 +
DEBUG_SGR_PROCESSING - decoding the <ESC>[ codes (that pair of bytes being the CSI "Control Sequence Introducer" - including the one ending in m which is the "Set Graphics Rendition" that Mudlet (and other MUD clients and other things) use to control colours and other font effects.
 +
DEBUG_OSC_PROCESSING - decode the <ESC>] codes (that MUST end with a <ESC>\) - currently Mudlet only handles a couple of these OSC "Operating System Commands".
 +
DEBUG_MXP_PROCESSING - stuff to do with the MXP protocol - which uses a <ESC> ... z sequence of characters to do some things...
 +
</nowiki>

Latest revision as of 08:52, 21 October 2024

If you just want to use Mudlet, you can skip these steps, and use one of the already ready (pre-compiled) installers ready for download.

Otherwise, hop in for new adventure!

Easy Mudlet code understanding.png

Compiling

Compiling on Ubuntu

These instructions will get you setup compiling on Ubuntu. Need a hand? Join us on Mudlet's Discord or forums.

Ubuntu 22.04 & later

Following instructions will work on Ubuntu 22.04 as well as all its flavours and derivatives (such as KDE Neon, for example) Important thing is to have Universe repository enabled in your package manager. (on Ubuntu you will have all the repositories that you need already enabled by default.)

1. necessary dependencies

Majority of required dependencies can be obtained from repositories, and can be installed with following command:

 sudo apt install ubuntu-restricted-extras qtcreator build-essential git zlib1g-dev libhunspell-dev \
  libpcre3-dev libzip-dev libboost-dev libboost-all-dev libyajl-dev libpulse-dev libpugixml-dev \
  liblua5.1-0-dev lua-filesystem lua-zip lua-sql-sqlite3 luarocks ccache lua5.1 libsecret-1-dev \
  libglu1-mesa-dev mesa-common-dev libglib2.0-dev libgstreamer1.0-dev libqt5opengl5-dev cmake \
  qt6-multimedia-dev libqt6core5compat6 qt6-tools-dev qtkeychain-qt6-dev qt6-l10n-tools ninja-build \
  qt6-tools-dev-tools libqt6core5compat6-dev qttools5-dev qtmultimedia5-dev qt6-speech-dev

1.1 Ubuntu 24.04:

sudo apt install qt6-multimedia-dev

Few of required Lua modules are not available in official repositories, so they have to be installed using luarocks

 sudo luarocks install lcf
 sudo luarocks install luautf8
 sudo luarocks install lua-yajl
 sudo luarocks install lrexlib-pcre

2. obtaining the source code

Obtain the latest in-development code with:

 git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 mkdir Mudlet/build
 cd Mudlet/build

3. compiling the code

 cmake .. -G Ninja
 ninja

4. installing compiled code

After successful code compilation, next few commands will install resulting binaries, desktop file for menus and appropriate icon.

 sudo make install
 sudo cp ../mudlet.png /usr/share/pixmaps
 sudo cp ../mudlet.desktop /usr/share/applications

5. optional additional software

One of the major reasons for compiling Mudlet from source is the ability to unlock more features that are not enabled in official AppImage. Manual compilation will resolve the issues with sound by using system provided libraries, as well as enable more detailed theming of Mudlet application itself. However, do take note that Mudlet is a Qt based program, and that theming will not 'just work' in GTK based desktop environments (Gnome, XFCE, MATE, Budgie).

 sudo apt install qt5ct

will install a tool for configuration of look and feel of Qt programs inside those desktop environments. Users of Qt based Desktop environments (KDE Plasma, LXQT) can simply use settings provided by environment itself.

Many of Qt widget styles and color schemes are available in official repositories, and will make Mudlet better.

6. Mudlet on Wayland

Mudlet compiled like this will run and work on Wayland, however, there are a few quirks with Keybidings (Numpad may not work as expected). Until that is resolved you may wish to start mudlet with:

 QT_QPA_PLATFORM=xcb mudlet

(enter in terminal or simply change the Exec= line in /usr/share/applications/mudlet.desktop)

7. uninstallation

You can reverse the process described in this guide with following command:

 sudo rm -fr /usr/bin/mudlet /usr/share/mudlet /usr/share/applications/mudlet.desktop /usr/share/pixmaps/mudlet.png

Other Ubuntu Versions

Most of the installation instructions for 22.04 should work for older versions as well. Of note is the required version of Qt, which is 5.14. If your used version of Ubuntu only supplies older Qt versions, have a look at Stephan Binners PPAs, which supplies a whole range of packages for different Ubuntu versions. Be sure to read the installation and usage instructions as Qt is installed to /opt and requires sourcing a script to set up.

Compiling on Chrome OS

These instructions will get you setup compiling on Chrome OS. Need a hand? Join us on Mudlet's Discord or forums.

1. Install dependencies

sudo apt install git build-essential \
  lua5.1 liblua5.1-0-dev libpcre3-dev libboost-dev zlib1g-dev cmake \
  libhunspell-dev lua-rex-pcre2 lua-sql-sqlite3 lua-filesystem lua-zip libyajl-dev \
  libzip-dev libglu1-mesa-dev ccache libpugixml-dev mesa-common-dev qtcreator \
  libpulse-dev libglib2.0-dev luarocks libboost-all-dev libsecret-1-dev \
  ninja-build libsecret-1-dev qt6-tools-dev qt6-5compat-dev qt6-multimedia-dev
sudo luarocks install luautf8
sudo luarocks install lua-yajl

3. Get Mudlet source

git clone --recursive https://github.com/Mudlet/Mudlet.git mudlet

4. Create a build directory

cd mudlet
mkdir build && cd build

5. Run the following command

cmake .. -G Ninja

then:

ninja -j 2

5. Start the application you have just compiled - enjoy

src/mudlet

Compiling on macOS

These instructions will get you setup compiling on macOS. Need a hand? Join us on Mudlet's Discord server or forums otherwise.


1. Install prerequisites

Install XCode, command line tools for XCode, and HomeBrew.

Once everything is installed, do:

 brew doctor
 brew update
 brew install git

2. Get Mudlet source

 git clone --recursive https://github.com/Mudlet/Mudlet.git 

3. Go to the parent of the mudlet "src" folder and create (if necessary) a build subdirectory (this is so that we can build out of source which keeps the source code clean)

 cd Mudlet && mkdir build

3. Setup your environment

 ./CI/travis.osx.before_install.sh
 ./CI/travis.osx.install.sh
 luarocks config lua_version 5.1
 eval `luarocks path --lua-version=5.1`

For the following, one may have to add _DIR="/opt/homebrew/" such as PCRE_DIR="/opt/homebrew/" or ZIP_DIR="/opt/homebrew/" if the installation could not find header files.

 luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install lrexlib-pcre PCRE_DIR=`brew --prefix pcre`
 brew install sqlite
 luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luasql-sqlite3 SQLITE_DIR=`brew --prefix sqlite` 
 luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luautf8
 luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install luafilesystem
 luarocks --lua-version=5.1 --lua-dir=`brew --prefix [email protected]` install lua-zip ZIP_DIR=`brew --prefix libzip`
 brew install boost

OK to answer yes to delete files if prompted for the rm command above.

4. Run the following commands

 cd build
 cmake ../../Mudlet -DCMAKE_PREFIX_PATH=`brew --prefix qt5`
 make -j `sysctl -n hw.ncpu`


5. Enjoy

The mudlet.app is now available in src/ for launching:

 open src/Mudlet.app

6. Qt Creator setup

No Lua installation is found, despite it existing on your system? Launch Qt Creator by doing open /Applications/Qt Creator.app (location depends on how you installed it).

Receiving a No rule to make target ... libQt5UiTools_debug.a error? A workaround is to symlink a file.

Mudlet in Qt Creator is not launching due to dyld: Symbol not found: __cg_jpeg_resync_to_restart? See here for a workaround.

7. (Optional) Discord Integration on ARM64

ARM64 binaries are not available libdiscord-rpc so you need to compile and combine it with the existing x86_64 binary into a universal binary.

git clone --single-branch --branch v3.3.0 https://github.com/discord/discord-rpc.git
cd discord-rpc
python build.py libs --shared
lipo ./builds/install/osx-dynamic/lib/libdiscord-rpc.dylib /path/to/existing/x86_64/libdiscord-rpc.dylib -output libdiscord-rpc.dylib -create
// verify that it's a universal binary:
otool -L libdiscord-rpc.dylib
// check it in to source control

8. Troubleshooting If you exhaust all efforts to get YAJL to compile on your local system with homebrew, clone from the YAJL repository then ./configure && sudo make install.

Compiling on Debian

1. Install required packages from main repo.

sudo apt-get install build-essential git liblua5.1-0-dev zlib1g-dev libhunspell-dev libpcre3-dev \
libzip-dev libboost-dev libyajl-dev libpulse-dev libsecret-1-dev lua-rex-pcre2 lua-filesystem lua-zip \
lua-sql-sqlite3 qt5-qmake qtmultimedia5-dev qttools5-dev luarocks ccache libpugixml-dev
sudo luarocks install luautf8
sudo luarocks install lua-yajl
sudo luarocks install lrexlib-pcre

2. Grab latest Mudlet source.

mkdir ~/projects && cd ~/projects && git clone --recursive https://github.com/Mudlet/Mudlet.git mudlet

3. Build Mudlet.

cd ~/projects/mudlet/src
qmake
make
sudo make install

4. (Optional) Discord library

If you get the following error;

Could not find Discord library - searched in:

you need to specify the discord library in your build. Run the following, changing the path where necessary;

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/user/mudlet-dev/Mudlet/3rdparty/discord/rpc/lib/

and recompile. You should see

Discord integration loaded. Using functions from: "libdiscord-rpc.so"

Compiling on Raspberry Pi OS

These instructions will get you compiling and running Mudlet on Raspberry Pi OS (Buster). Need a hand? Join us on Mudlet's Discord or forums.

1.a Install apt dependencies

sudo apt-get update
sudo apt-get install build-essential git liblua5.1-dev zlib1g-dev libhunspell-dev libpcre3-dev \
  libzip-dev libboost-graph-dev libyajl-dev libpulse-dev lua-rex-pcre2 lua-filesystem lua-zip \
  lua-sql-sqlite3 qt5-assistant qtmultimedia5-dev qttools5-dev luarocks ccache libpugixml-dev cmake


installing apt dependencies

1.b Install luarocks dependencies

sudo luarocks install luautf8
sudo luarocks install lrexlib-pcre
sudo luarocks install lua-yajl YAJL_LIBDIR=`find /usr -name "libyajl.so" -printf '%h\n'` YAJL_INCDIR=/usr/include


after luarocks dependencies

2. Get Mudlet source

mkdir ~/source && cd ~/source 
git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
After cloning

3. Create a build directory

 cd Mudlet && mkdir build && cd build

4. Run the following commands to build

WITH_UPDATER=NO WITH_3DMAPPER=NO qmake ../src/mudlet.pro
If you get a response along the lines of:
qmake: could not find a Qt installation of 
then you likely have qtchooser present in your system that allows for both Qt4 and Qt5 (or more than one Qt5 version) and it modifiers qmake and some other Qt development programs to take an additional argument to specify which version to use. In that case you should use:
WITH_UPDATER=NO WITH_3DMAPPER=NO qmake -qt=qt5 ../src/mudlet.pro
After qmake

THEN:

For the fastest compile time while still being able to use the system at all (~35min on a RPi4 with 4GB of ram)
make -j $(expr `nproc` - 1)

OR:

Use this if you have an older Raspberry Pi. Be prepared for it to take a while (over an hour) - it is not recommended to try to more than one compilation task at a time on the older systems with the -j option as they will only have a system memory with enough space for one of some of those tasks:
make
Success!

4. Install the application you have just compiled

sudo make install
Installed now

5. Enjoy!

# mudlet is in the path, can just run it
mudlet

Compiling on Arch Linux

AUR Install and Compile

Mudlet is available in the Arch User Repository. (If the AUR has become unmaintained/orphaned, then skip below to Manual install.)

To install it use your favourite AUR helper (helper tool will automatically resove dependancies); example using yay :

yay -S mudlet

For more info on this process, visit Arch User Repository - ArchWiki.

Note: For the most recent development version of Mudlet, replace 'mudlet' with 'mudlet-git' in the above commands and proceed as described.

Built in fonts have been disabled, but are available in packages listed as optional dependancies.

Discord support in Mudlet depends on an external library provided by discord-rpc-api, which is also available in AUR, choose whichever variant suits you best.

Manual Install and Compile

These instructions will get you setup compiling on Arch. Need a hand? Join us on Mudlet's Discord or forums.

1. necessary dependencies

Majority of required dependencies can be obtained from repositories, and can be installed with following command:

 sudo pacman -S --needed cmake qt5-multimedia hunspell libzip lua51-filesystem qt5-gamepad lua51-luautf8 pugixml \
  ttf-font qtkeychain-qt5 boost qt5-tools ttf-bitstream-vera ttf-ubuntu-font-family noto-fonts-emoji glu luarocks

Few of required Lua modules are not available in official repositories, so they have to be installed using luarocks

 sudo lua5.1 /usr/bin/luarocks install lcf
 sudo lua5.1 /usr/bin/luarocks install luautf8
 sudo lua5.1 /usr/bin/luarocks install lua-yajl
 sudo lua5.1 /usr/bin/luarocks install lrexlib-pcre
 sudo lua5.1 /usr/bin/luarocks install luasql-sqlite3
 sudo lua5.1 /usr/bin/luarocks install lua-zip

There is an optional dependency for discord integration:

 git clone https://github.com/discord/discord-rpc
 cd discord-rpc
 mkdir build
 cd build
 cmake .. -DCMAKE_INSTALL_PREFIX=/usr
 sudo cmake --build . --config Release --target install

2. obtaining the source code

Obtain the latest in-development code with:

 git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 mkdir Mudlet/build
 cd Mudlet/build

3. compiling the code

There below are two ways to build with qmake, the first is for general use, the second is for developers:

 qmake ../src/mudlet.pro

*OR*

 qmake CONFIG+=debug ../src/mudlet.pro

Now finish compiling:

 make -j `nproc`

4. installing compiled code

After successful code compilation, next few commands will install resulting binaries, desktop file for menus and appropriate icon.

 sudo make install
 sudo cp ../mudlet.png /usr/share/pixmaps
 sudo cp ../mudlet.desktop /usr/share/applications

5. optional additional software

One of the major reasons for compiling Mudlet from source is the ability to unlock more features that are not enabled in official AppImage. Manual compilation will resolve the issues with sound by using system provided libraries, as well as enable more detailed theming of Mudlet application itself. However, do take note that Mudlet is a Qt based program, and that theming will not 'just work' in GTK based desktop environments (Gnome, XFCE, MATE, Budgie).

 sudo pacman -S install qt5ct

will install a tool for configuration of look and feel of Qt programs inside those desktop environments.↵Users of Qt based Desktop environments (KDE Plasma, LXQT) can simply use settings provided by environment itself.

Many of Qt widget styles and color schemes are available in official repositories, and will make Mudlet better.

6. Mudlet on Wayland

Mudlet compiled like this will run and work on Wayland, however, there are a few quirks with Keybindings (Numpad may not work as expected). Until that is resolved you may wish to start mudlet with:

 QT_QPA_PLATFORM=xcb mudlet

(enter in terminal or simply change the Exec= line in /usr/share/applications/mudlet.desktop)

7. uninstallation

You can reverse the process described in this guide with following command:

 sudo rm -fr /usr/bin/mudlet /usr/share/mudlet /usr/share/applications/mudlet.desktop /usr/share/pixmaps/mudlet.png

Compiling on Fedora (aarch64)

1.  Install dependencies

sudo dnf groupinstall "Development Tools" "Development Libraries"
sudo dnf install compat-lua compat-lua-devel compat-lua-libs hunspell-devel lua5.1-filesystem luarocks pugixml-devel qtkeychain-qt5-devel bitstream-vera-fonts-all ccache qt-creator qt5-qtmultimedia-devel qt5-qtgamepad-devel yajl-devel qtchooser qt5-qttools-devel qt5-qttools-static zziplib-devel pcre-devel libzip-devel sqlite-devel
sudo luarocks --lua-version 5.1 --tree=/usr install luazip
sudo luarocks --lua-version 5.1 --tree=/usr install luasql-sqlite3
sudo luarocks --lua-version 5.1 --tree=/usr install lcf
sudo luarocks --lua-version 5.1 --tree=/usr install luautf8
sudo luarocks --lua-version 5.1 --tree=/usr install lua-yajl
sudo luarocks --lua-version 5.1 --tree=/usr install lrexlib-pcre

In your user's home directory:

If you use a bash shell:

luarocks --lua-version 5.1 path --no-bin >> .bashenv
source .bashenv

If you use a zsh shell:

luarocks --lua-version 5.1 path --no-bin >> .zshenv
source .zshenv

If you use a csh shell:

luarocks --lua-version 5.1 path --no-bin >> .cshenv
source .cshenv

This should cover paths, but you may want to reboot to be sure.

2. Obtain the source code

git clone --recursive --branch=development https://github.com/Mudlet/Mudlet.git
mkdir Mudlet/build
cd Mudlet/src

3. Make necessary compiling instruction adjustments

Edit mudlet.pro - find these lines in mudlet.pro and make the following changes:

    linux {
        LIBS += \
            -llua5.1 \
            -lhunspell
        INCLUDEPATH += /usr/include/lua5.1
    }

We're adding a - between lua and 5.1 and adding -1.7 to hunspell under LIBS so that it becomes this:

    linux {
        LIBS += \
            -llua-5.1 \
            -lhunspell-1.7
        INCLUDEPATH += /usr/include/lua5.1
    }

Save and exit.

4. Compile

cd ../build

Run this in the build directory:

WITH_FONTS=NO WITH_OWN_QTKEYCHAIN=NO WITH_UPDATER=NO WITH_VARIABLE_SPLASH_SCREEN=NO XDG_DATA_DIRS=/usr/share qmake-qt5 PREFIX=/usr INCLUDEPATH+=/usr/include/lua-5.1 LUA_SEARCH_OUT=lua-5.1 ../src/mudlet.pro

An explanation of the qmake arguments -- we're passing these environment variables to mudlet.pro:

WITH_FONTS=NO WITH_OWN_KEYCHAIN=NO WITH_UPDATER=NO WITH_VARIABLE_SPLASH_SCREEN=NO XDG_DATA_DIRS=/usr/share

Adding build variables to mudlet.pro so that it finds the correct libraries:

PREFIX=/usr INCLUDEPATH+=/usr/include/lua-5.1

And finally adding a build variable to translations/translated/updateqm.pri so that it uses the correct version of the Lua compiler (Fedora also comes with 5.4) to generate translation statistics.

LUA_SEARCH_OUT=lua-5.1

Once complete, run the following:

If you have time to kill (About 10 minutes on an Apple M1 Max in Fedora):

make

If you want it done as fast as possible(Less than a minute on an Apple M1 Max in Fedora):

make -j `nproc`

Or if you want something in between, make -j `nproc` tells it to use all available processor cores.  If you want to use a specific number instead (ie 2), you can use:

make -j 2

5. Install

sudo make install
sudo cp ../mudlet.png /usr/share/pixmaps
sudo cp ../mudlet.desktop /usr/share/applications

6. Hang onto the cloned git repo If you need to uninstall, you can go back into the /build directory and 'sudo make uninstall'.

Compiling on Gentoo

An overlay containing Mudlet is available for compiling Mudlet on Gentoo.

Compiling on Windows

  • At the end of installation uncheck run msys2 now and click finish
  • Run MSYS2 MINGW64 from the start menu
  • Run the following in the opened MSYS2 terminal (you right-click in order to paste):
pacman --files --refresh
pacman --sync git mingw-w64-x86_64-qt-creator mingw-w64-x86_64-cmake mingw-w64-x86_64-ninja mingw-w64-x86_64-clang-libs --noconfirm
  • Run the following from the MSYS2 terminal:
git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
  • Setup the development environment (~5-10min) by running:
./Mudlet/CI/setup-windows-sdk.sh 

Take note of the message at the end to add the variables to your environment once you have opened the project in Qt Creator. (WITH_MAIN_BUILD_SYSTEM, MINGW_BASE_DIR, LUA_PATH, LUA_CPATH)

Windows environment variables.png

Note Note: This might not work on windows arm64, pacman freezes.

  • Open Qt Creator. You will need to open it via MSYS2 every time:
/mingw64/bin/qtcreator.exe
  • Press link with Qt on the bottom right of Qt Creator
Link with qt.png
  • Choose C:/msys64/mingw64 as the location then restart Qt Creator
Qt location.png
  • Open project; C:/msys64/home/<user>/Mudlet/src/mudlet.pro
Open new project - qtcreator.png
  • In Build Environment details, set environment variables to what was stated in the sdk-setup script above.
Build environmental variables.png
  • Build Mudlet (Ctrl+B)
  • Run Mudlet (Ctrl+R)


Contributing changes

Once you're all done with your changes, contribute them to Mudlet using a pull request. Thanks for improving open-source!

Compiling on Github Codespaces

Github Codespaces allow you to code and run Mudlet all from the browser - makes it a lot easier to get started. It also allows you to code Mudlet itself from any computer in the world!

1. Create a new codespace

Create a new Codespace by going to https://github.com/Mudlet/Mudlet using Google Chrome or Microsoft Edge (Firefox at the time of the writing doesn't have working copy/paste). There, click the green "Code" button, select the "Codespaces" tab and click "New codespace".

New codespace screenshot

2. Wait for it to load

This will take a while (~5min) so grab a tea:

Building Visual Studio Codespace.png

3. Connect to the environment

Go to the Ports section at the bottom and change the Port Privacy of the Open Mudlet port to Public:

Port privacy in Github Codespaces.png


Then connect to your online Linux desktop with mudlet as the password by clicking on the web icon.

Connect to remote machine.png


In case it can't connect, make sure the port privacy is set to Public. If it still can't connect, try 4-5 more times - eventually it'll work.


We chose a retro 90's look here to fit with the whole hacking theme, so if you see this you're good 😉

4. Build Mudlet

In Codespaces, hit F7 and select Let CMake guess...

CMake configuration.png

It will then start building Mudlet automatically. Using the Basic instance (only kind available in beta) the first-time build will take ~25min, so take a break here - you've made excellent progress. All follow-up compiles after this will be quicker, by the way.

Building Mudlet in codespaces.png

5. Run Mudlet

Launch Mudlet.png

Hit the little play button at the bottom of the screen, and Mudlet will now launch in the remote connection tab. Not working? We can help. Otherwise, enjoy!

Mudlet running remotely.png

Note: When the codespace is unused for a while, it will disconnect. It'll never disconnect while you're actively using it. See Github issue for details.

Developing with Docker

Docker is a system designed for more reproducible and isolated builds. A docker setup exists and has been tested using Pop OS! 20.04 (which is derived from Ubuntu 20.04). First, follow the instructions to install both docker and docker-compose.

Clone the development branch

 git clone --recursive -b development https://github.com/Mudlet/Mudlet.git
 cd Mudlet/docker

Make a local copy of the .env.template file:

 cp .env.template .env

If you wish to customize things like the number of cores to use for building mudlet, feel free to change the corresponding values in the .env file.

To run Qt-Creator and develop Mudlet, run docker-compose up dev.

To run Mudlet, run docker-compose up mudlet. Note: At the moment, the mudlet build will not persist settings past container rebuilds.

Setting up IDEs

CLion

Qt not detected

If you'd like to use CLion and it is giving the following error:

    By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
    asked CMake to find a package configuration file provided by "Qt5Core", but
    CMake did not find one.

    ...
  

You can fix this by setting -DCMAKE_PREFIX_PATH=<your Qt + version + compiler location>. For example: -DCMAKE_PREFIX_PATH=/media/vadi/SSDer/Programs/Qt/5.14.2/gcc_64/

CLion CMake settings - finidng Qt.png

CLion setup on Windows

After running setup-windows-sdk.ps1 make sure to set Cmake options to:

-DCMAKE_PREFIX_PATH=C:\Qt\Tools\mingw730_32;C:\Qt\5.14.2\mingw73_32 -DBoost_INCLUDE_DIR=C:\Libraries\boost_1_77_0

Directories might vary slightly, when different Qt, Boost or MinGW version will be used.

Clion Settings - Cmake.png


You will need 32 bit version of MinGW. Set it in the Toolset field to:

C:\Qt\Tools\mingw730_32

Directory may be slightly different if MinGW version used will change.

Toolchain.png

Clang Tidy

Ensure that CLion is set to run the project's .clang-tidy checks with the Prefer .clang-tidy files over IDE settings option:

Clang Tidy CLIon.png

This helps us catch any issues just a bit earlier.

Checking memory leaks & other issues (sanitizers)

Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:

  • LeakSanitizer for detecting memory leaks
  • AddressSanitizer for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
  • UndefinedBehaviourSanitizer for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
  • MemorySanitizer for detecting reading uninitialised memory
  • ThreadSanitizer for detecting threading issues

To use the sanitisers, set the USE_SANITIZER CMake variable to one or several variables (separate by comma): Address, Memory, MemoryWithOrigins, Undefined, Thread, or Leak

To use them in CLion, adjust the CMake settings:

Clion cmake settings.png

Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.

Clang Format

Ensure that CLion is set to use the .clang-format formatting style:

Clang-format CLion.png

This helps keep the look'n'feel of the source code in a consistent manner, even with many people contributing to Mudlet.

Visual Studio Code

To set the path in Visual Studio Code, open settings, search for cmake environment and set the CMAKE_PREFIX_PATH to your path, such as /home/vadi/Programs/Qt/5.15.2/gcc_64:

CMake path in Visual Studio Code.png

Clang Tidy

clang-tidy catches common programming issues, run it by selecting 'Analysis' from the command palette (Ctrl+Shift+P by default):

Clang-tidy in vscode.png

It is also possible check status of analysis and cancel if needed.

Checking memory leaks & other issues (sanitizers)

Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:

  • LeakSanitizer for detecting memory leaks
  • AddressSanitizer for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
  • UndefinedBehaviourSanitizer for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
  • MemorySanitizer for detecting reading uninitialised memory
  • ThreadSanitizer for detecting threading issues

To use the sanitisers, set the USE_SANITIZER CMake variable to one or several variables (separate by comma): Address, Memory, MemoryWithOrigins, Undefined, Thread, or Leak

To use them in VSCode, set the cmake.configureSettings variable:

Cmake.configureSettings option in vscode.png

Choosing which sanitizers in vscode to use.png

Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.

Qt Creator

Clang Tidy and Clazy

Configure Mudlet-specific checks for clang-tidy and clazy tools help catch any issues early on. See Qt Creator's instructions for setting this up - clang-tidy can use the .clang-tidy file that's available at the root of the repository, and for clazy enable level0 and level1 checks.

Clang tidy configuration.png
Clazy configuration.png

Checking memory leaks & other issues (sanitizers)

Besides clang-tidy, it's also possible to enable clang sanitizers to double-check for issues:

  • LeakSanitizer for detecting memory leaks
  • AddressSanitizer for detecting most issues dealing with memory, such as out of bounds accesses to heap, stack, global and more
  • UndefinedBehaviourSanitizer for detecting the use of various features of C/C++ that are explicitly listed as resulting in undefined behaviour (such as using misaligned or null pointer, conversion to, from, or between floating-point types which would overflow the destination, division by zero, etc)
  • MemorySanitizer for detecting reading uninitialised memory
  • ThreadSanitizer for detecting threading issues

To use the sanitisers, set the USE_SANITIZER CMake variable to one or several variables (separate by comma): Address, Memory, MemoryWithOrigins, Undefined, Thread, or Leak

To use them in Qt creator, head to Projects - Build:

Sanitisers in qt creator.png

Not all sanitisers can be used with each other - in that case the cmake configuration won't allow you to continue.

Clang Format

Ensure that Qt Creator is set to use the .clang-format formatting style in the C++ settings. Turn on Format instead of indenting for Ctrl+I to format code, and ensure Override Clang Format configuration file is disabled:

Qt Creator clang format.png

This helps keep the look'n'feel of the source code in a consistent manner, even with many people contributing to Mudlet.

Building with multiple versions of Lua

Mudlet uses Lua 5.1 only, so if you are compiling on a system that also has later versions installed, you might get the following error: ‘LUA_GLOBALSINDEX’ was not declared in this scope.

To fix this, pass the path to Lua headers explicitly. For CMake: -DLUA_INCLUDE_DIR=/usr/include/lua5.1 (adjust as needed).

Key contributing information

Clang format is used to automatically format code submissions using the src/.clang-format style. See here how to enable clang-format with Qt Creator - and make sure to specify the 'File' option for the configuration style.

Branches:

development is the development branch where new features can go.

Workflow:

Fork and submit a PR with your changes (Github tutorial).

Here is a list of package versions delivered with different Linux distros. You may want to upgrade these: https://repology.org/project/mudlet/versions

Lua & Luarocks

Mudlet includes a Lua (version 5.1) scripting system for the end-user, which you, as a reader of this Wiki, may already be aware of! If not, you might wish to (after you have got your hands on a working Mudlet) take a look at Mudlet Lua API as that is the recommended place to find out the details of all the functions that Mudlet provides on top of the core Lua functionality.

Some of that ability comes from extra code that is not built-in to Lua but is in the form of external modules either in the form of script (text) files written in the Lua language itself or binary (library) files compiled from (usually but not exclusively 'C') source code. In order to have that functionality Mudlet makes use of several of these modules which can most readily (if not already available as "packages" for a particular Operating System) be obtained as rocks from the public Luarocks collection. Such a rock actually consists of a rockspec file that gives instructions to the Luarocks tool how to obtains the (source) code, compile it on any supported OS into the form that a Lua interpreter (including the one included in each running Mudlet profile) can use, and where and what it will be placed and called when it has been made. After that it should be available to Lua via the require command.

Anyone compiling Mudlet for themselves will find it desirable to ensure they have a usable Luarocks installation and have the lua-yajl module installed before commencing to compile Mudlet itself; this is because a Lua (version 5.1) interpreter and that module are used within the build process of making the executable code that is the Mudlet application.

Included Modules

  1. luautf8 (manual in README)
  2. lcf (customised version)
  3. luafilesystem (manual)
  4. lrexlib-pcre (manual)
  5. luasql-sqlite3 (http://lunarmodules.github.io/luasql/manual.html manual)
  6. lua-yajl (manual in README)
  7. luazip (manual)

Adding Luarocks

Here's a rundown on checking you can use luarocks. Here we will use the bit32 module as an example.


1. Install via luarocks

> luarocks install bit32

2. Check where luarocks installs the modules. Note the modules section.

> luarocks show bit32

bit32 5.3.5.1-1 - Lua 5.2 bit manipulation library

bit32 is the native Lua 5.2 bit manipulation library, in the version from Lua 5.3; it is compatible with Lua 5.1, 5.2, 5.3 and 5.4.

License:        MIT
Homepage:       http://www.lua.org/manual/5.2/manual.html#6.7
Installed in:   /usr/local

Modules:
        bit32 (/usr/local/lib/lua/5.1/bit32.so)

Depends on:
        lua >= 5.1, < 5.5 (using 5.1-1)

3. Recompile mudlet. You may need to adjust lua path and cpath information for your environment. You can use the following commands to help find this information.

> luarocks --lua-version 5.1 path --no-bin
export LUA_PATH='./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;/home/username/.luarocks/share/lua/5.1/?.lua;/home/username/.luarocks/share/lua/5.1/?/init.lua'
export LUA_CPATH='./?.so;/usr/local/lib/lua/5.1/?.so;/usr/lib/x86_64-linux-gnu/lua/5.1/?.so;/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;/home/username/.luarocks/lib/lua/5.1/?.so

Or from within mudlet itself you can issue these commands to double check the correct paths are being used.

> lua print(package.path)
/home/username/.config/mudlet/profiles/localhost/?.lua;/home/zooka/.config/mudlet/profiles/localhost/?/init.lua;./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua;/home/username/.luarocks/share/lua/5.1/?.lua;/home/username/.luarocks/share/lua/5.1/?/init.lua 
   
> lua print(package.cpath)
/home/username/.config/mudlet/profiles/localhost/?.so;/home/username/Workspace/mudlet-dev/Mudlet/build/lib/?.so;./?.so;/usr/local/lib/lua/5.1/?.so;/usr/lib/x86_64-linux-gnu/lua/5.1/?.so;/usr/lib/lua/5.1/?.so;/usr/local/lib/lua/5.1/loadall.so;/home/username/.luarocks/lib/lua/5.1/?.so

4. Recompile and run a test script using the require command to load in the necessary library.

bit32 = require("bit32")

function bit32_test()
  bit32.band(0,1)
end

Enabling Debug Build

To enable a debug build that can be run through GDB:

  • follow all steps until qmake
  • modify the qmake line by adding in debug info, e.g.:
 qmake CONFIG+=debug ../src/mudlet.pro
  • compile as normal
  • attach gdb to mudlet
 gdb ./mudlet
  • within gdb command line start mudlet running by:
 run
  • proceed to crash mudlet then type
 bt
  • submit the output with your bug reports.

Compile Time Flags

DEBUG_UTF8_PROCESSING - for decoding the UTF-8 (1 byte with the MSB set or 2, 3 or 4 bytes) encoding
DEBUG_GB_PROCESSING - for decoding the GBK (2 bytes) or GB18030 (2 or 4 bytes) encodiing
DEBUG_BIG5_PROCESSING - for decoding the Big5-ETEN or Big5-HKSCS encodings
DEBUG_EUC_KR_PROCESSING - for decoding the EUC_KR encoding
DEBUG_SGR_PROCESSING - decoding the <ESC>[ codes (that pair of bytes being the CSI "Control Sequence Introducer" - including the one ending in m which is the "Set Graphics Rendition" that Mudlet (and other MUD clients and other things) use to control colours and other font effects.
DEBUG_OSC_PROCESSING - decode the <ESC>] codes (that MUST end with a <ESC>\) - currently Mudlet only handles a couple of these OSC "Operating System Commands".
DEBUG_MXP_PROCESSING - stuff to do with the MXP protocol - which uses a <ESC> ... z sequence of characters to do some things...