Build Instructions for MS Windows Platform
The directory mmex/build/msw-vc-2013e has the project files for:
Visual Studio Community 2013.
For other compilers, see the readme file in the mmex/build/msw directory.
||Visual Studio Version
||Visual Studio Community 2013
||Visual Studio Community 2013
||Not Supported for development.
1. Installation of the following software:
Visual Studio Community 2013
Environment variable need to access the wxWidgets build on Windows.
||Location of wxWidgets 3.0.2
How to setting up Environment variables using Windows 7
Control Panel ---> System and Security ---> System
Advanced system settings (Located on left navigation panel)
System Properties (Dialog) ---> Advanced (Tab)
Environment Variables (Button)
GitHub Windows https://windows.github.com/
A Windows interface to GitHub to download the source code.
Allows documentation to be obtained from the source code.
Allows the generation of .po and .mo files required for language translations.
GNU GetText for Windows: http://gnuwin32.sourceforge.net/packages/gettext.htm.
This package may also be required on systems to allow translations to work.
Append path to bin folder of installed software to PATH environment variable
(usually "C:\Program Files\GnuWin32\bin").
To build the setup installation, download and install InnoSetup Quick Start Pack.
This includes InnoSetup itself and Inno Setup Preprocessor. Append the folder
path to the Windows Environment Variable: PATH for the installed software.
(something like a "C:\Program Files\Inno Setup 5")
wxWidgets must be built using MS VC Community 2013, to ensure a successful build.
- Ensure Prerequisites are complete with an installation of wxWidgets 3.0.2
or greater, compiled using MS VC Community 2013
- Using MS VC Community 2013 the project file in the wxWidgets 3.0.2 folder.
Using MS VC Community 2013, build the appropriate configurations for your needs.
Recommended configurations for mmex: Release and Debug
Additional information on how to install and build wxWidgets can be found here
- using MS VC Community 2013, locate the directory: moneymanagerex\build\msw-vc-2013e.
Open the project file: moneymanagerex\build\msw-vc-2013e\mmex.sln
MS VC++ 2013e will set up the project files to the user's environment.
- In the Solution Explorer set the mmex project as the Startup Project.
- Using the Build ->Configurations Manager...
Select one of following configurations to build:
Release <-- Best choice for most people.
Debug <-- Extra debug code added for debugging and may be slower.
- Build the mmex solution...
- Locate and Run the batch file: update_mmex_build_files.bat
The IDE build locations will be updated with the required support files to successfully
run MMEX within the MS VC++ 2013e IDE.
This can be done in 2 ways.
- Directly from https://github.com/moneymanagerex/moneymanagerex and using the Download Zip link.
- (Recommended)Using tools such as Git for Windows or TortoiseGit.
Downloading source code using GitHub and TortoiseGit
- Install GitHub for Windows and/or Git
Both versions have a Git implementation which is required for TortoiseGit.
- Install TortoiseGit.
TortoiseGit will need the location of Git if it cannot determine where it is.
- Create a directory/folder where the MMEX repository will reside, for example c:\Dev.
- Using Windows Explorer, right-mouse-click on your new folder and use the TortoiseGit Command:
Dialog box info:
Directory: This will be automatically provided by TortoiseGit
Check Box Select: Recursive
Select button: OK
This will now download the repository to your machine, including all sub modules used by moneymanagerex.
The same for command line is:
git clone https://github.com/moneymanagerex/moneymanagerex
git submodule update --init
Using GitHub to submit changes.
For this you will need your active GitHub account.
- Using the GitHub MoneyManagerEx page, via your Internet Web browser,
Select the option: Fork
This will create a copy of the repository to your own local account.
- Change the settings of your local MMEX repository as follows:
Use the TortoiseGit Commmand:
- In the dialog navigation tree, select: Git -> Remote
You should see a remote location: origin
Select it to reveal the URL as set up above.
- Add a new remote location: upstream
This will point to the same URL
- Change the URL for origin to your YOUR_GITHUB_USERNAME
Using Git terminology, you will now be able to pull changes from upstream,
and push the changes to your origin repository on GitHub. Using the web interface,
you can now create a pull request. This will submit your proposed changes to MMEX.
End of File.