Build directory for both debug and release is lmc\build. lmc |-build | |-debug | |-release |-src

However, the output files are configured to be written to separate debug and release folders at the same level as src. lmc |-debug |-release |-src

The custom build step needs the following parameters: Command: scripts\buildwin32.bat Working directory: %{sourceDir} Command arguments: %{buildDir}..\debug (for debug) Command arguments: %{buildDir}..\release release (for release)

For building the installer, run setup.bat in lmc\setup\win32 folder. NSIS must be installed first. The batch file executes an NSIS script (setup.nsi) to generate the installer. The NSIS script contains two variables called ProductVersion and InstallerVersion that must be set whenever the application version changes. The installer generated will have the name lmc--win32.exe and it will be saved to lmc\setup folder.

Build directory for debug is lmc/debug. Build directory for release is lmc/release. lmc |-debug |-release |-src

The custom build script needs executable permission. Run the following command: chmod 755 ./scripts/buildx11

The custom build step needs the following parameters: Command: ./scripts/buildx11 Working directory: %{sourceDir} Command arguments: %{buildDir}

The two script files named lan-messenger.sh and whitelist are needed to launch the application. The first one sets the load paths for all libraries needed by the application. The second is needed for adding the application to Ubuntu's whitelist so that the system tray icon can be shown. The second script will be called internally by the first script. Make sure both scripts have permission to run as executables. chmod 755 ./lan-messenger.sh chmod 755 ./whitelist

Note: The custom build script will take care of this automatically.

To debug a running application, run this command before attaching to the process: echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope

This will be valid only for the current session. It has to be run again after a log out or restart.

For building the installer, run the bash script "setup" in lmc/setup/x11 folder. Make sure the scripts named "postinst", "postrm" and "prerm" in the folder package/DEBIAN have executable permission. The file "control" in the same folder should be edited to reflect the proper version and installed size (in KB) of the application. The scripts "lmc" and "whitelist" in package/usr/bin must also have executable permission. All files and folder inside package folder must be owned by root user.

The setup script generates the deb installation package which will be saved to lmc/setup folder. The package will have the name lmc__i386.deb. For generating rpm package, alien must be installed first. To install alien, run: sudo apt-get install alien Execute "rpm_setup" script in lmc/setup/x11 to generate an rpm package from the deb package (deb package must be created first). This package will have the name lmc--2.i386.rpm and will be saved to lmc/setup folder.

Build directory for debug is lmc/debug. Build directory for release is lmc/release. lmc |-debug |-release |-src

The custom build script needs executable permission. Run the following command: chmod 755 ./scripts/buildmacos

The custom build step needs the following parameters: Command: ./scripts/buildmacos Working directory: %{sourceDir} Command arguments: %{buildDir}/LAN-Messenger.app/Contents/MacOS

For building the installer, first run the bash script "createdisk" in lmc/setup/mac folder. This will create a disk image and copy all the required files needed for the application to it. Now open up the disk image, set the background image, icon size (96x96), icon position, icon arrangment (Snap to Grid) and window size. Now run the script "addlicense" to add the user license and compress the disk image. The dmg file will have the name lmc__intel.dmg and will be saved to lmc/setup folder.