npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cunit-manager

v0.0.15

Published

CUnit enables simple CMake dependency management

Downloads

15

Readme

logo

c-unit

CUnit is the answer to c/c++ dependency management in the CMake world. It comes as an amalgamation of other attempts including awesome projects like mason, hunter & conan.

We feel that each of those projects have respective shortcomings and based on all of them, we have designed c-unit to be best in breed.

note c-unit has a strong emphasis on creating statically linked binary distributions, therefore most default recipes are for static compilation. You are more than welcome to create shared lib recipes and publish them.

Furthermore, you can issue global cmake override flags converting all dependencies to shared libs

install

cu is implemented in JS for flexibility, so installation anywhere is dead simple.

npm i -g cunit-manager

Repos and Recipes

cu works with recipes in repositories. The global default repository is here: github.com/cunit/cunits

note you can add your own repos public or private both locally and git based as follows

# GITHUB EXAMPLE PUBLIC OR PRIVATE
cunit repo add https://github.com/myorg/my-cunits.git
# OR A LOCAL DIR
cunit repo add file:///var/cunits-local-on-disk

A recipe is super simple

name: opencv
repository: 
  url: https://github.com/opencv/opencv.git

cmake:
  flags:
    CMAKE_BUILD_TYPE: Release
    BUILD_SHARED_LIBS: OFF
    BUILD_JPEG: OFF
    BUILD_JASPER: OFF
    BUILD_PNG: ON
    BUILD_ZLIB: ON
    BUILD_IPP_IW: OFF
    BUILD_ITT: OFF
    BUILD_JAVA: OFF
    BUILD_PROTOBUF: OFF
    WITH_PROTOBUF: OFF
    WITH_CAROTENE: OFF
    WITH_CUBLAS: OFF
    WITH_CUDA: OFF
    WITH_CUFFT: OFF
    WITH_FFMPEG: OFF
    WITH_GPHOTO2: OFF
    WITH_GSTREAMER: OFF
    WITH_GTK: OFF
    WITH_ITT: OFF
    WITH_IPP: OFF
    WITH_JASPER: OFF
    WITH_LAPACK: OFF
    WITH_MATLAB: OFF
    WITH_NVCUVID: OFF
    WITH_OPENCL: OFF
    WITH_OPENCLAMDBLAS: OFF
    WITH_OPENCLAMDFFT: OFF
    WITH_OPENEXR: OFF
    WITH_PTHREADS_PF: OFF
    WITH_V4L: OFF
    WITH_WEBP: OFF
  findTemplate: cmake/FindOpenCV.cmake.hbs

dependencies:
  libtiff: Release-v4-0-9
  zlib: v1.2.11
  libpng: v1.6.33
  libjpeg: 8.4.0

Quickstart

It takes a few simple steps.

  • Create a cunit.yml file in the root of your project
name: cunit-example

dependencies:
  protobuf: 3.1.0
  opencv: 3.4.1

tools:
	protobuf: 3.1.0
  • Then run configure
cunit project configure
  • In your root CMakeLists.txt BEFORE your project declaration add something like the following:
cmake_minimum_required(VERSION 3.10)

# INSERT THIS LINE
include(${CMAKE_CURRENT_LIST_DIR}/.cunit/cunit.cmake)

project(cunit_example)

Cross-Compiling "Toolchains"

Create your standard cmake toolchain file and use it as follows:

name: cunit-example
profiles: [Debug,Release]

toolchains:
  "aarch64-linux-gnu": cmake/aarch64.cmake 
  # file would be at this relative location from the project root

dependencies:
  protobuf: 3.1.0
  opencv: 3.4.1

In order to use with non-cmake dependencies and scripts add the following to the top of your toolchain file:

include(${CMAKE_CURRENT_LIST_DIR}/.cunit/cunit.toolchain.cmake)

and add the following to the bottom of your toolchain file

cunit_toolchain_export()