All Projects â†’ cfillion â†’ Reapack

cfillion / Reapack

Licence: lgpl-3.0
đŸ“Ļ Package manager for REAPER

Projects that are alternatives of or similar to Reapack

Scarf
An experimental prototype of a package manager and packaging ecosystem. Currently being rebuilt.
Stars: ✭ 108 (-21.17%)
Mutual labels:  package-manager
Pnpm
Fast, disk space efficient package manager -- åŋĢ速įš„īŧŒčŠ‚įœįŖį›˜įŠē间įš„包įŽĄį†åˇĨå…ˇ
Stars: ✭ 14,219 (+10278.83%)
Mutual labels:  package-manager
Core Plans
Core Habitat Plan definitions
Stars: ✭ 129 (-5.84%)
Mutual labels:  package-manager
Alire
Command-line tool from the Alire project and supporting library
Stars: ✭ 108 (-21.17%)
Mutual labels:  package-manager
Mint
A package manager that installs and runs executable Swift packages
Stars: ✭ 1,750 (+1177.37%)
Mutual labels:  package-manager
Gitdependencyresolverforunity
This plugin resolves git url dependencies in the package for Unity Package Manager. You can use a git url as a package dependency!
Stars: ✭ 126 (-8.03%)
Mutual labels:  package-manager
Raven
Raven is a Package Manager for Chez Scheme
Stars: ✭ 107 (-21.9%)
Mutual labels:  package-manager
Topgrade
Upgrade everything
Stars: ✭ 2,074 (+1413.87%)
Mutual labels:  package-manager
Baget
A lightweight NuGet and symbol server
Stars: ✭ 1,861 (+1258.39%)
Mutual labels:  package-manager
Tiny Package Manager
Learn how npm or Yarn v1 works.
Stars: ✭ 125 (-8.76%)
Mutual labels:  package-manager
Bpkg
Lightweight bash package manager
Stars: ✭ 1,601 (+1068.61%)
Mutual labels:  package-manager
Haxelib
The Haxe library manager
Stars: ✭ 119 (-13.14%)
Mutual labels:  package-manager
Integration
HACS gives you a powerful UI to handle downloads of all your custom needs.
Stars: ✭ 2,114 (+1443.07%)
Mutual labels:  package-manager
Pkgverse
đŸ“Ļ🔭🌠 Create your own universe of packages à la tidyverse
Stars: ✭ 108 (-21.17%)
Mutual labels:  package-manager
Termux Apt Repo
Script to create Termux apt repositories.
Stars: ✭ 131 (-4.38%)
Mutual labels:  package-manager
Yarn
The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
Stars: ✭ 40,325 (+29334.31%)
Mutual labels:  package-manager
Gyro
A zig package manager with an index, build runner, and build dependencies
Stars: ✭ 126 (-8.03%)
Mutual labels:  package-manager
Pip Check
pip-check gives you a quick overview of all installed packages and their update status.
Stars: ✭ 134 (-2.19%)
Mutual labels:  package-manager
Paq Nvim
🌚 Neovim package manager
Stars: ✭ 131 (-4.38%)
Mutual labels:  package-manager
Swiftbrew
Homebrew for Swift packages
Stars: ✭ 129 (-5.84%)
Mutual labels:  package-manager

ReaPack: Package manager for REAPER

Build status Donate

Visit the ReaPack website for ready-to-use binaries, the user guide or the package upload tool.

Building from source

Clone the repository and submodules:

git clone --recursive https://github.com/cfillion/reapack.git

Prerequisites

Software requirements:

  • CMake 3.15 or newer
  • C++17 compiler (MSVC on Windows)
  • PHP (Linux and macOS only)

Linux

Install the following libraries (and development headers if your system provides them separately):

macOS

Install Boost and Catch2 using Homebrew (recommended). The build tools can be installed using xcode-select --install or the Xcode IDE.

Windows

MSVC can be installed with the Build Tools for Visual Studio or the Visual Studio IDE.

Use the x64 or x86 Native Tools Command Prompt for VS 20XX matching the target architecture when configuring or building ReaPack.

Install vcpkg in any directory:

git clone https://github.com/Microsoft/vcpkg.git C:\path\to\vcpkg
C:\path\to\vcpkg\bootstrap-vcpkg.bat

Set the VCPKG_ROOT and VCPKG_DEFAULT_TRIPLET environment variables (only required when running vcpkg install or creating a new build tree):

set VCPKG_ROOT=C:\path\to\vcpkg
set VCPKG_DEFAULT_TRIPLET=%PLATFORM%-windows-static

Install ReaPack's build dependencies:

set /p reapack-deps=<vendor\vcpkg-deps.txt
%VCPKG_ROOT%\vcpkg install %reapack-deps%

Build configuration

Create and configure a new build tree inside of the build directory.

cmake -B build -DCMAKE_BUILD_TYPE=Debug

Using the Ninja generator is recommended for best performances:

cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Debug

Alternatively, multiple build trees can be created if desired:

cmake -B build/debug    -DCMAKE_BUILD_TYPE=Debug
cmake -B build/release  -DCMAKE_BUILD_TYPE=Release
cmake -B build/portable -DCMAKE_BUILD_TYPE=RelWithDebInfo \
  -DCMAKE_INSTALL_PREFIX=/path/to/reaper/portable/install

The vcpkg install is automatically detected and configured from the VCPKG_ROOT and VCPKG_DEFAULT_TRIPLET environment variables when creating a build tree on Windows.

Compile and install

To compile a build tree:

cmake --build build

To install ReaPack into your REAPER installation after building:

cmake --build build --target install

The following targets are available:

  • all: Build ReaPack (default target)
  • clean: Delete all generated files (can be run before building another target using --clean-first)
  • install: Build and install ReaPack into REAPER's resource directory (as specified in CMAKE_INSTALL_PREFIX)
  • test: Build and run the test suite

Cross-compilation

Linux

g++-$TOOLCHAIN_PREFIX will be used when compiling for architectures other than i686. Libraries for the target architecture are expected to be in /usr/{include,lib}/$TOOLCHAIN_PREFIX, /usr/$TOOLCHAIN_PREFIX/{include,lib} or /usr/lib32.

ARCH=i686 TOOLCHAIN_PREFIX=i386-linux-gnu \
  cmake -B build/i686 -DCMAKE_TOOLCHAIN_FILE=cmake/linux-cross.cmake

ARCH=armv7l TOOLCHAIN_PREFIX=arm-linux-gnueabihf \
  cmake -B build/arm32 -DCMAKE_TOOLCHAIN_FILE=cmake/linux-cross.cmake

ARCH=aarch64 TOOLCHAIN_PREFIX=aarch64-linux-gnu \
  cmake -B build/arm64 -DCMAKE_TOOLCHAIN_FILE=cmake/linux-cross.cmake

macOS

macOS 10.14 or older, Xcode 9 and the latest Clang (brew install llvm) are required for producing 32-bit builds.

cmake -B build \
  -DCMAKE_BUILD_TYPE=Release \
  -DCMAKE_OSX_ARCHITECTURES=i386 \
  -DCMAKE_OSX_DEPLOYMENT_TARGET=10.9 \
  -DCMAKE_TOOLCHAIN_FILE=cmake/brew-llvm.cmake

Support and feedback

Ask any ReaPack-releated questions in the ReaPack forum thread. Questions related to development or packaging can be asked in the development thread.

Report bugs or request features in the issue tracker. Send code contributions as pull requests.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].