multimake

KO | EN

gitlite — search

#hacktoberfest #react #typescript #llm #golang #android #rust #deep-learning #docker #windows #kubernetes #security #openai #open-source

(★ 8)

A tool which helps building multiple software packages at once

multimake Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Main Page
=========

Introduction
------------

This documentation describes the Multimake package.
The purpose of this software is to help you build multiple software packages at once for your system. The tool handles package dependencies in such a way that every package is built only as soon as all the required dependencies have been built.

Features
--------

- Parallel build. Several packages can be built simultaneously if they don't have interdependencies.
- Support of CMake packages
- Support of QMake packages
- Support of Automake packages
- Support of Maven packages
- Support of package installation in non-standard location (prefix)

Design
------

The package is a thin wrapper around the "ExternalProject" CMake module. It provides macros which are more convenient to use than the ones of "ExternalProject".

Examples
--------

Examples can be found in the [examples](examples/README.md) folder

Known limitations
-----------------

- Dependee packages must be defined before dependers.

Tips
----

- If a specific package is already available in your system, or if you simply want CMake not to build it, you can add the following command. Note that this line must be written before the package is defined:
```
add_available_package(packageName)
```

- You can also exclude a package by adding it to the "EXCLUDED_PACKAGES" variable. By using that technique, you can reuse an existing "CMakeLists.txt" file. Example:
```
  $ PATH=$PATH:/Path/To/Layer1:/Path/To/Layer2; cmake -DEXCLUDED_PACKAGES="package1;package2" -DCMAKE_INSTALL_PREFIX=/My/Install/Prefix /Path/To/Folder/Containing/MyCMakeLists.txt
```

- By default, the "master" branch of a component is used. If you want to use a specific branch/tag/commit, you can use the following line. That line must be before the definition of the package:
```
set_external_git_project_commit(packageName branch-or-tag-or-commitID)
```

Reference
---------

Some variables can be set before adding a package, in order to override the default behavior.

| Variable name              |      Description              | Default behavior/value                          |
|----------------------------|:-----------------------------:|---------------------------------------:|
| PackageName_INSTALL_PREFIX | package installation prefix   | ${CMAKE_INSTALL_PREFIX}, which defaults to "/usr/local" |
| PackageName_NO_INSTALL | If set to "1", disables the installation ("make install") | "make install" is called every time the build is triggered |
| PackageName_BUILD_ALWAYS | When set to "0", the package will not be rebuilt if it has been successfully built once | "make" is called every time the build is triggered |
| PackageName_GIT_COMMIT | specifies the GIT commit or branch to be checked out | "master" |

### Example

```
    set(gammaray_GIT_COMMIT v2.6.0)
    add_cmake_external_git_project(gammaray "git://github.com/KDAB/GammaRay.git" "qt" "" "")
```

TODO
----

- Make the generated "make" file executable.

FAQ
---

- Q : How can I rebuild only one package without building its dependencies ?
 
   A : Use the following command :
```
$ sh make PackageToRebuild/fast
```

- Q : How can I build all the dependencies of a package ?
 
   A : Use the following command :
```
$ sh make PackageToRebuild_deps
```

- Q : How can I install the packages on a non-standard location (different from /usr/local).

A : When invoking cmake to prepare your build folder, set the CMAKE_INSTALL_PREFIX variable:
   ```
   $ PATH=$PATH:/Path/To/Layer1:/Path/To/Layer2; cmake -DCMAKE_INSTALL_PREFIX=/My/Install/Prefix /Path/To/Folder/Containing/MyCMakeLists.txt
   ```
   
 - Q : How can I choose between Release/Debug mode when building the packages ?

A : You can specify the value of the boolean option called "ENABLE_DEBUG" when invoking cmake::
   ```
   $ PATH=$PATH:/Path/To/Layer1:/Path/To/Layer2; cmake -DENABLE_DEBUG=OFF /Path/To/Folder/Containing/MyCMakeLists.txt
   ```
   Note that the default value is "ON", which means packages are built in debug mode by default. 
   
   
 - Q : What if there is a package which I do not want to be installed (no "make install")
 
   A : You can set the "*_NO_INSTALL" variable to 1 before adding your package. Example:
```
set(MyPackage_NO_INSTALL 1)
add_cmake_external_project(MyPackage MyPackageLocation "Package2;...." "-DMyConfigurationOption=blabla;...")
```

- Q : How do I mark a package to always be rebuilt ("make" called even if it has already successfully been built) 
 
   A : You can set the "*_BUILD_ALWAYS" variable to 1 before adding your package. Example:
```
set(MyPackage_BUILD_ALWAYS 1)
add_cmake_external_project(MyPackage MyPackageLocation "Package2;...." "-DMyConfigurationOption=blabla;...")
```

multimake

multimake Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

multimake

multimake Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README