Today I took some time aside to update the slightly outdated Marble installer for Windows. It now covers the latest stable release Marble 1.8.3. Before pushing it to our Installation website I’d like some quick feedback from other Windows users willing to give it a try: Does Marble run fine on your system after installing it? The installer also associates .kml and .gpx files with Marble such that you can open them directly from e.g. Windows Explorer. Download the installer here: marble-setup-1.8.3.exe.
Quick ad intervention: If you like this please donate for the KDE Randa sprint. I’d like to meet with fellow Marble developers to discuss future development. Thanks
Since I don’t plan to step up as a maintainer for our Windows installer it would be great if someone else interested in Windows packages could look into some possible improvements. Compiling against quazip would result in .kmz support. Also the installer ain’t the most pretty nor smart thing in the universe yet; forcing an uninstall of older Marble versions before the installation would be a good start. Since it is based on NSIS improvements shouldn’t be too hard to implement. Interested? It’s quite painless to set things up:
- Install some compiler, the free MSVC express editions suffice (I used MSVC 2010 Express)
- Install Qt, the binary Windows packages are fine (I used 4.8.6 for VS 2010).
- Clone the Marble repository (msysgit is your friend)
- Install cmake (I used 184.108.40.206)
- Have cmake generate a MSVC solution for you:
cmake -G "Visual Studio 10" -DQTONLY=TRUE -DWITH_DESIGNER_PLUGINS=FALSE -DCMAKE_INSTALL_PREFIX=../export ../src
- Open the generated marble.sln. Inside MSVC open the configuration manager and switch from Debug to Release. Compile. Also build the INSTALL target.
- Install NSIS. Open src/marble.nsi in some sane text editor and change the srcdir variable to your export folder. Use the NSIS compiler to generate marble-setup.exe from src/marble.nsi.