Difference between revisions of "HowTo compile with cmake"

From AMule Project FAQ
Jump to: navigation, search
(→‎libpng)
(Added instructions for zlib.)
 
Line 51: Line 51:
 
=== wxWidgets ===
 
=== wxWidgets ===
 
*Just open the project that suits your IDE and build the whole solution.
 
*Just open the project that suits your IDE and build the whole solution.
 +
 +
=== zlib ===
 +
*zlib ships an useable cmake-project.
 +
**Open the dir where you extracted the source and point your cmake-gui to that dir. Build dir can point to the same dir.
 +
**Configure the project
 +
**adjust the install paths to a new dir. Recommended one beside you aMule build-dir.
 +
**Generate and open the project.
 +
**Build the install target.
  
 
== Preparing the libraries needed to build with MinGW based systems ==
 
== Preparing the libraries needed to build with MinGW based systems ==

Latest revision as of 12:34, 6 March 2020

Requirements for compiling aMule for Windows using cmake

You will need the following packages:

Unpacking the sources

  • Create a root folder. You can name it whatever you want. In this example it is called "aMule".
  • Unpack wx, cryptopp and flex/bison into that folder. (Just to find them again. In fact it doesn't matter where put them.
  • Unpack zlib, rename the folder to zlib only (without version) and place it in the same directory as you libpng sources.

Preparing the libraries needed to build with visual studio

boost

  • Open a Visual Studio Command Prompt from your startmenu
  • cd into the dir, where you extracted the source
  • run bootstrap
  • run b2 install

cryptopp

  • If you use VisualStudio, open one of the projects you find in the source-dir. For others instructions will go here, when tested.
  • Select Release or Debug build.

This is important, as cryptlib.h will be generated and compile will only work with the same config. This also means, if you've built cryptopp with Debug option, you can build aMule only with Debug enabled I'll recommend anyway to always build both types

  • Right click on cryptlib goto Properties C/C++ -> Code Generation and set the Runtime-Library to /MD (/MDd for Debug)
  • Build the cryptlib project in the solution

libGeoIP

  • Open a Visual Studio Command Prompt from your startmenu
  • cd into the dir, where you extracted the source
  • run nmake /f Makefile.vc

libpng

  • Open die vstudio project
  • When using Visual Studio 2019
    • Open the properties of libpng, got to C/C++ -> All Options and change the warning-level to max /W3 on Debug and Release config
    • Repeat'the above for zlib
  • Build the libpng project of the solution.

wxWidgets

  • Just open the project that suits your IDE and build the whole solution.

zlib

  • zlib ships an useable cmake-project.
    • Open the dir where you extracted the source and point your cmake-gui to that dir. Build dir can point to the same dir.
    • Configure the project
    • adjust the install paths to a new dir. Recommended one beside you aMule build-dir.
    • Generate and open the project.
    • Build the install target.

Preparing the libraries needed to build with MinGW based systems

boost

  • Open an cmdline
  • switch to <boostDir>
  • Run bootstrap gcc
  • Run .\b2 install --toolset=gcc

cryptopp

  • The version from github has a CMakeLists.txt, so just open and configure it.
  • Open the file <cryptoppDir>/config.h
  • Compile with the tools you generated a Makefile for.

libGeoIP

  • Open an editor and create a new file with this content:

ADD_LIBRARY (libGeoIP 

   GeoIP.c
   GeoIP_deprecated.c
   GeoIPCity.c;regionName.c
   timeZone.c

)

TARGET_COMPILE_DEFINITIONS (libGeoIP 

   PRIVATE PACKAGE_VERSION="1.6.3"

)

  • Save this file in geoipDir/LibGeoIP/ with name CMakeLists.txt
  • Open cmake-gui, configure it
  • Open use to compile, with anything you generated build-files for.

libpng

  • Thankfully libpng comes with an CMakeLists.txt, so you can just use cmake to compile everything.

wxWidgets

  • Open an cmdline
  • switch to <wxDir>/build/msw
  • Run mingw32-make -f makefile.gcc BUILD=release UNICODE=1 SHARED=1 CXXFLAGS=-std=gnu++11
  • Run mingw32-make -f makefile.gcc UNICODE=1 SHARED=1 CXXFLAGS=-std=gnu++11

Preparing aMule

  • Start GIT-GUI (or git-bash or anything you like) from your start-menu (or whatever your current installation has).
  • Point the repo to https://github.com/amule-project/amule.git and clone it to whereever you want.
  • Checkout branch cmake.

Creating the solution

  • Open cmake-gui
  • Point the source-code directory to where you cloned the repo
  • Point the build directory to wherever you want
  • Hit configure and select the generator for the IDE you want to use and click finish.
  • Now you can select all the options you want, and hit configure again.
  • Hit generate

Setting the paths needed

If (and it will be the case if you didn't move anything you downloaded or compiled into system directories) not everything needed is found.

  • For the libraries: Open a Texteditor, open <your-amule-folder>\cmake\searchdirs.cmake
    • Turn on advanced view in cmake-gui (I prefer to enable grouped view, too). Now you can set the dirs to search (take the opened file as hint).
    • Uncomment the needed lines, and point it to where the stuff was created.
  • For the binaries (flex/bison) you can select the files directly in cmake (i.e BISON_EXECUTABLE for bison) after enabling advanced opton.
  • Hit configure again
  • Hit generate

Compiling

  • Open the created project files in the build directory you've set.
  • Choose Debug/Release etc. like you selected for cryptopp before.
  • Start compilation.

Tested with

  • Microsoft Visual C++ 2010 (VC10) Download
  • Microsoft Visual Studio 2012 (VC11) (official download-link is dead)
  • Microsoft Visual Studio 2013 (VC12) (official download-link is dead)
  • Microsoft Visual Studio 2015 (VC14) (official download-link is dead)
Retrieved from "http://wiki.amule.org/w/index.php?title=HowTo_compile_with_cmake&oldid=28777"