Hello Tobias, I'm here again :)

I'm trying to use your process management system to speed up biicode Boost builds (I'm having timeouts on my travis ci builds due to Boost.Log build). Since Travis expects output, my idea was to get your process_start_script() and run each library build job as a separate process, then wait for all. If that works as expected, there will be no timeout since your process_wait_all() prints some fancy progress output.

It works like a charm, I have it on a testing branch but I'm sure it will be part of the biicode Boost setup.

I have a couple of suggestions/questions:

• Custom progress information: I will be glad if some form of progress customization is made. The ....1/3... is great, but I think a bit of customization could improve a lot UX. In my case, I prompt Starting [boost lib] build job... before starting each script, one per line, will be great to print something similar when the process finishes [boost lib] build job finished. Maybe a callback on_success()/on_fail() approach?
• Portability: As far I know the implementation uses system dependent scripting to achieve process management. To be able to use this features on biicode, I need support on Windows, linux, and mac. I remember a conversation where you pointed out that you are using PS on windows and bash on linux. Will this work on Darwin/Mac OSX too?

.. to save time, disk space and bandwidth .. to allow the use of cmakepp in build systems that diable network access during the build

I am willing to help with that.

Martin

I have a list of filenames without file extensions, and now I want to create two new derived lists which each add different file extensions to each list entry. E.g. in pseudocode:

set(files filea fileb) set(sources lists_map(${files}, function(el) {return el ++ ".c"})) set(headers lists_map(${files}, function(el) {return el ++ ".h"}))

On Windows, read_line

• can't handle a leading = character (it crashes)
• strips any leading spaces from the input
• expands any variables (e.g. if the user enters %path%, the stored result is the value of the user's path environment variable rather than the string %path%).

This patch fixes these issues.

Add a function "string_set_char_at" (and unit tests) which corresponds to "string_char_at" in order to be able to set an abritary char in a string. Indexing is identical to "string_char_at". Example call: string_set_char_at(1 "hello" a) -> returns "hallo"

One example shows how to download cmakepp when it is not available, directly from cmake. While that is very neat, I'm concerned about relying on github (and a working internet connection) for a build. Is there a release I can just drop in the project directory?

A title case algorithm written in cmake for cmakepp. It automatically tries to set the title case of a sentence. Example: "my simple title" -> "My Simple Title" It tries to keep certain words in lower case, as set by a style guide (easily changed). Caveat: it only works for English sentences correctly. Use case example: documentation, where title case might be useful for a section

currently complex constraints (constraints other than true,false or null) only allow {optional:true|false}

these dependency constraints should allow more. (e.g. content_dir = relative path to package is linked to content dir of dependency)

version constraints...

This way it's easy to print progress status based on that seed. It's not a real progress value, but a seed to be used to generate output.

I'm using it to generate dynamic ellipsis output with \r on the boost-biicode scripts.

Overview

This is an attempt to start to streamline the documentation of the cmake/string function folder. At the same time, the corresponding tests were created/extended/streamlined in order to ensure a more thorough testing.

What was added:

• Comments what each function does and specifying the type of input and output
• Create a reasonable unit test base line
• Bug fixes due to testing

TODO

• Validate the documentation: errors, form
• Validate that the changed API has no further side effects
• Finish the documentation. A few functions are missing.

Caveat

For a few functions, the order of the parameters were changed (hence the API changes). I tried to update the calls and tests seemingly work (cmake -P cmakepp.cmake test_execute_glob_parallel "tests//.cmake"). However, executing "cmake -P build/script.cmake" fails (same as the master itself?)

Hi,

I've added cmake 3.0.1 version to travis-ci config. Seems that some test fails with message:

CMake Error at cmake/core/message.cmake:142 (_message):

'assertion failed1: '1.0.0-+;STREQUAL;1.0.0''

curl -OL https://raw.github.com/toeb/cmakepp/master/install.cmake && cmake -P install.cmake && rm install.cmake

on macOS 11.4 (20F71) with cmake version 3.21.2

In semver_parse.cmake, you have:

 set(semver_identifier_regex "[0-9A-Za-z-]+")
 set(semver_major_regex "[0-9]+")
 set(semver_minor_regex "[0-9]+")
 set(semver_patch_regex "[0-9]+")
 set(semver_identifiers_regex "${semver_identifier_regex}(\\.${semver_identifier_regex})*") 
 set(semver_prerelease_regex "${semver_identifiers_regex}")
 set(semver_metadata_regex "${semver_identifiers_regex}")
 set(semver_version_regex "(${semver_major_regex})\\.(${semver_minor_regex})\\.(${semver_patch_regex})")
 set(semver_regex "(${semver_version_regex})(-${semver_prerelease_regex})?(\\+${semver_metadata_regex})?")

I am not familiar with the cmake language, but I don't see where any of this excludes leading zeroes in numeric fields. As per the SemVer 2.0 spec, numeric fields may appear in the version triple (either major, minor or patch) and in prerelease fields (fields are dot delimited), and they may not have leading zeros. The following version strings are not SemVer compliant:

• 01.0.0 // Leading zero in major field.
• 1.01.0 // Leading zero in minor field.
• 1.0.01 // Leading zero in patch filed.
• 1.0.0-01 // Leading zero in prerelease field.
• 1.0.0-1.01 // Leading zero in prerelease field.

Please see the suggested regex's provided near the end of the FAQ and the discussion threads that eventually lead to their adoption, particularly the minimal set of oracles used to test them.

For major, minor and patch, you should have (0|[1-9]\d*), and prerelease is something like (?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-zA-Z-][0-9a-zA-Z-]*))*. The reason for the more complex prerelease part is due to the fact that a prerelease tag consists of either numeric or alphanumeric fields, delimited by periods.

Based on what you have in that file, I think you would also reject a valid SemVer strings of the form 1.0.0+meta and 1.0.0-prr+meta.1.

README.rd (4c20943) says: "Use the Biicode Block" but that URL (https://www.biicode.com/toeb/cmakepp) gives a scary security warning in Firefox.

I'm getting deprecation warnings of policies CMP0053 and CMP0054, running CMake 3.12.3 on macOS.

CMake Deprecation Warning at submodules/cmakepp/cmakepp.cmake:25 (cmake_policy):
  The OLD behavior for policy CMP0053 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:15 (include)


CMake Deprecation Warning at submodules/cmakepp/cmakepp.cmake:28 (cmake_policy):
  The OLD behavior for policy CMP0054 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.
Call Stack (most recent call first):
  CMakeLists.txt:15 (include)

Personally I didn't get any errors when setting both policies to NEW, but I'm only using the following functions from CMake++.

• semver_parse
• ans
• scope_import_map

Hi @toeb ,

Hope you are all well !

I was wondering how CMake++ could help me to manage different types of external project schemes and to cache some cross-platform build with a project version + toolchain tag.

Goal:

• Support of CMake, QMake, Automake, Maven packages or some package installation in non-standard location packages (prefix) (eg link)
• Support a registry of C/C++ packages, or stack of packages, with specific CMake args, and trigger some override commands for custom POST_BUILD actions (eg copy all runtime libraries with dependencies libraries to custom install prefix)
• Support packages or project manifests (eg. with CMake++ with a JSON or YAML like FIPS and create on the fly CMake package configuration files for external project with a namespace (eg. link)
• Analyze and generate external projects config file with the list of targets and options into a JSON or YAML file. (Would be useful to disable options incompatible with some platforms, (eg for iPhoneOS and Android builds, BLAS libraries are not all compatible)

Questions:

1. I prefer YAML formats as more human readable and more easy to connect with some other scripts (often Golang based for my part) but I could not make fully work the yaml function from the test function. Is it something that you intend to implement soon ? It would work perfectly with FIPS ^^ ?

2. Would it be possible to have an example with CMake++ building an OpenCV project and some dependencies like Caffe for mobile without conflicting with the server version Caffe or tensorflow or tiny-dnn with your recent additions on package functions (link ? (more precisely I cannot get if it could manage some kind of build/install cache strategy like hunter per toolchains and prevent duplicate builds of dependencies like Protobuf for example but still be able to set custom args per platfroms ^^)

3. Would it be possible to see such project build example with a cross-platform approach using toolchains from either Polly or FIPS with CMake++ ?

4. Is it possible to create executable wrappers from a list of vcs uris and install their pre-requisiste ? (eg. install and wrap CppSharp requires a wrap around premake5, mono, xbuild and nuget in order to wrap CppSharp-Cli ? (eg link) (btw, I am working with an Apple laptop)

Thanks for this awesome project Tobias ! Have an awesome week !

Cheers, Richard

Hi,

hope you are all well !

I tried to build the example, described on your blog (link), and I got the following errors.

1. eigen3 is not included
2. several CMake Warning

Errors:

  Cannot set "__ans": current scope has no parent.
Call Stack (most recent call first):
  /opt/local/share/cmake-3.7/Modules/Compiler/Clang.cmake:7 (return)
  /opt/local/share/cmake-3.7/Modules/Compiler/AppleClang-CXX.cmake:1 (include)
  /opt/local/share/cmake-3.7/Modules/CMakeCXXInformation.cmake:25 (include)
  cmakepp.cmake:5706 (_project)
  CMakeLists.txt:26 (project)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at cmakepp.cmake:11098 (set):
  Cannot set "__ans": current scope has no parent.
Call Stack (most recent call first):
  /opt/local/share/cmake-3.7/Modules/Platform/Darwin-Clang.cmake:7 (return)
  /opt/local/share/cmake-3.7/Modules/Platform/Darwin-Clang-CXX.cmake:1 (include)
  /opt/local/share/cmake-3.7/Modules/Platform/Darwin-AppleClang-CXX.cmake:1 (include)
  /opt/local/share/cmake-3.7/Modules/CMakeCXXInformation.cmake:48 (include)
  cmakepp.cmake:5706 (_project)
  CMakeLists.txt:26 (project)
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
{
 "myproject":{
  "name":"myproject",
  "directory":"/Users/Luccio/cpp/cmakepp",
  "targets":{
   "name":"myexe",
   "project_name":"myproject"
  }
 }
}
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/Luccio/cpp/cmakepp/_builds
Scanning dependencies of target myexe
[ 50%] Building CXX object CMakeFiles/myexe.dir/main.cpp.o
/Users/Luccio/cpp/cmakepp/main.cpp:3:10: fatal error: 'Eigen/Dense' file not found
#include <Eigen/Dense>
         ^
1 error generated.
gmake[2]: *** [CMakeFiles/myexe.dir/build.make:63: CMakeFiles/myexe.dir/main.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:68: CMakeFiles/myexe.dir/all] Error 2
gmake: *** [Makefile:84: all] Error 2

CMakeLists.txt:

cmake_minimum_required(VERSION 2.8.12)
## CMakeLists.txt for a simple project 
set(current_dir "${CMAKE_CURRENT_SOURCE_DIR}")
## get cmakepp
if(NOT EXISTS "${current_dir}/cmakepp.cmake")
  file(DOWNLOAD "https://github.com/toeb/cmakepp/releases/download/v0.3.1-alpha/cmakepp.cmake" "${current_dir}/cmakepp.cmake")
endif()

include("${current_dir}/cmakepp.cmake")

if(NOT EXISTS ${current_dir}/dependencies/eigen3)
 message(STATUS "installing Eigen3 from bitbucket")
 pull_package(eigen/eigen?tag=3.1.0 ${current_dir}/dependencies/eigen3)
 ans(package_handle)
 if(NOT package_handle)
  message(FATAL_ERROR "could not pull Eigen3")
 endif()
 ## print the package information returned
 json_print(${package_handle})

 message(STATUS "${current_dir}/dependencies/eigen3")

endif()

## from here on everything can be a normal cmakelists file
project(myproject)

include_directories("dependencies/eigen3")

fwrite("main.cpp" "
#include <iostream>
#include <Eigen/Dense>
using Eigen::MatrixXd;
int main()
{
  MatrixXd m(2,2);
  m(0,0) = 3;
  m(1,0) = 2.5;
  m(0,1) = -1;
  m(1,1) = m(1,0) + m(0,1);
  std::cout << m << std::endl;
}
")
add_executable(myexe "main.cpp")

print_project_tree()
print_targets()

Is there any way to solve these issues ?

Bonus questions:

Did you ever thought or start to develop some toolchains management for cmakepp ?

My use case is aimed for building cross-platform unity3d plugins for iOS, Android, WSA, MacOSX and Linux of CMake driven project (eg. Tensorflow)

More precisely, it would be really cool to manage a list of toolchains like Polly and some dockerized transpilers like with Dockcross.

It would help to create a template through cmake, as I would like to create a build bot to replace such bash scripts:

#!/bin/bash

## ##################################################################################################################################
# Copyright (c) 2017, Rosco Pecoltran
# All rights reserved.
## ##################################################################################################################################

set -e

clear ## clear terminal screen
pwd ## check current workdir

## #################################################################
## Project SDK name
## #################################################################

if [ ! -z "$1" ]; then
    PROJECT_NAME="$1"  # Custom SDK name (eg. SnipAR in order to gather in on Unity3D project all packages build, per platforms)
else
    echo "[Sniper] No arguments supplied for output SDK name"
    PROJECT_NAME="Eigen3" # Default output SDK name
fi

## #################################################################
## Project CMake Arguments
## #################################################################

PROJECT_CMAKE_ARGS_FILE=$(basename "$0" .sh) # filename to source inside the sniper bots ENV/CMake args for cross-compilation build with polly
PROJECT_CMAKE_HOME="." # home directory hosting root CMakeLists.txt

## #################################################################
## Project Global Arguments
## #################################################################

PROJECT_BUILD_TYPE="Release" # Release/Debug
PROJECT_LIBRARY_TARGET="eigen3" # Target name, libname ouput

## #################################################################
## Project VCS settings
## #################################################################

PROJECT_VCS_URL="https://github.com/hunter-packages/eigen"
PROJECT_VCS_BRANCH="hunter-3.3.1"

# notes: build package 
# - common:
#  - iOS (static libs)
#    - Architectures: i386, x86_64
#  - MacOSX (shared libs)
#    - Architectures: i386, x86_64
#  - Android (shared libs)
#    - Architectures: armv7a, armv7a-neon, arm64-v8a, x86, x86-64, mips, mips64
# - extras:
#  - Apple Frameworks (shared libs): iOS, MacOSX

## #################################################################
## Project Sniper Bot - settings
## #################################################################

SNIPER_BOTS_SCRIPT="bundle-unity3d.sh" # script filename to use for creating the new bundle of libraries

# Prefix Path with All SNIPER Bots Scripts
SNIPER_WORKDIR_DIR=$(pwd)
SNIPER_BOTS_PREFIX_PATH="./scripts"
SNIPER_BOTS_COMMAND="${SNIPER_BOTS_PREFIX_PATH}/${SNIPER_BOTS_SCRIPT}"
chmod a+x ${SNIPER_BOTS_COMMAND}

# Note: 
#  - enable/disable global settings for those helepers, please check: ./config/_init_.sh
SNIPER_BOTS_CONFIG_HELPERS_PREFIX_PATH="./config"
SNIPER_BOTS_CONFIG_HELPERS_INIT="_init_.sh"

# load global configuration settings for sniper bots dependencies (Polly, Hunter)
. ${SNIPER_BOTS_CONFIG_HELPERS_PREFIX_PATH}/${SNIPER_BOTS_CONFIG_HELPERS_INIT}

## #################################################################
## project build common arguments
## #################################################################

# common flags
PROJECT_BUILD_EXAMPLES=OFF
PROJECT_BUILD_TESTS=OFF
PROJECT_BUILD_DOCS=OFF

# libprotobuf-lite
PROJECT_COMMON_BUILD_ARGS=\
(
    "HUNTER_CONFIGURATION_TYPES=${PROJECT_BUILD_TYPE}"
    # build
    "EIGEN_BUILD_BTL=OFF"
    "EIGEN_BUILD_PKGCONFIG=ON"
    "EIGEN_DEFAULT_TO_ROW_MAJOR=OFF"
    "EIGEN_SPLIT_LARGE_TESTS=ON"
    # tests
    "EIGEN_FAILTEST=${PROJECT_BUILD_TESTS}"
    "BUILD_TESTING=${PROJECT_BUILD_DOCS}"
    "EIGEN_TEST_SSE2=OFF"
    "EIGEN_TEST_SSE3=OFF"
    "EIGEN_TEST_SSSE3=OFF"
    "EIGEN_TEST_SSE4_1=OFF"
    "EIGEN_TEST_SSE4_2=OFF"
    "EIGEN_TEST_AVX=OFF"
    "EIGEN_TEST_FMA=OFF"
    "EIGEN_TEST_AVX512=OFF"
    "EIGEN_TEST_F16C=OFF"
    "EIGEN_TEST_ALTIVEC=OFF"
    "EIGEN_TEST_VSX=OFF"
    "EIGEN_TEST_NEON=OFF"
    "EIGEN_TEST_NEON64=OFF"
    "EIGEN_TEST_ZVECTOR=OFF"
    "EIGEN_TEST_OPENMP=OFF"
    "EIGEN_TEST_SSE2=OFF"
    "EIGEN_TEST_NO_EXPLICIT_VECTORIZATION=OFF"
    "EIGEN_TEST_X87=OFF"
    "EIGEN_TEST_32BIT=OFF"
    "EIGEN_TEST_SYCL=OFF"
)

# Apple Frameworks - iOS and MacOSX 
PROJECT_BUILD_ARGS_UNITY3D_APPLE_FRAMEWORKS=\
(
    "BUILD_SHARED_LIBS=ON"
)

# PROJECT_PUBLIC_HEADERS_PREFIX_PATH=""

# iOS armv7, arm64
PROJECT_BUILD_ARGS_UNITY3D_APPLE_IOS=\
(
    "BUILD_SHARED_LIBS=OFF"
)

# MacOSX i386, x86_64
PROJECT_BUILD_ARGS_UNITY3D_APPLE_OSX=\
(
    "BUILD_SHARED_LIBS=ON"
)

# Android arm
PROJECT_BUILD_ARGS_UNITY3D_ANDROID=\
(
    "BUILD_SHARED_LIBS=ON"
)

# Linux
PROJECT_BUILD_ARGS_UNITY3D_LINUX=\
(
    "BUILD_SHARED_LIBS=ON"
)

# Windows WSA / SDK8.1 / PhoneSDK8.1
PROJECT_BUILD_ARGS_UNITY3D_WSA=\
(
    "BUILD_SHARED_LIBS=ON"
)

## #################################################################
## project build - active platforms/toolchains
## #################################################################

SNIPER_BOT_QUEUE_DEV=(\
    # Apple
    UNITY3D_APPLE_OSX_FRAMEWORK=TRUE        
    UNITY3D_APPLE_IOS_FRAMEWORK=TRUE            
)

SNIPER_BOT_QUEUE=(\
    UNITY3D_APPLE_OSX_FRAMEWORK=TRUE
    UNITY3D_APPLE_MACOSX=TRUE
    UNITY3D_APPLE_IOS_FRAMEWORK=TRUE
    UNITY3D_APPLE_IOS=TRUE
    UNITY3D_ANDROID_ARMEABI_V7A_NEON=TRUE
    UNITY3D_ANDROID_ARMEABI_V7A=TRUE
    UNITY3D_ANDROID_ARM64_V8A=TRUE
    UNITY3D_ANDROID_X86=TRUE
    UNITY3D_ANDROID_X86_64=TRUE
    UNITY3D_ANDROID_MIPS=TRUE
    UNITY3D_ANDROID_MIPS64=TRUE
    UNITY3D_LINUX_X86=TRUE
    UNITY3D_LINUX_X86_64=TRUE
    UNITY3D_WSA_PHONESDK81_ARM=TRUE
    UNITY3D_WSA_PHONESDK81_X86=TRUE
    UNITY3D_WSA_SDK81_ARM=TRUE
    UNITY3D_WSA_SDK81_X86=TRUE
    UNITY3D_WSA_SDK81_X64=TRUE
    UNITY3D_WSA_UWP_ARM=TRUE
    UNITY3D_WSA_UWP_X86=TRUE
    UNITY3D_WSA_UWP_X64=TRUE
)

## #################################################################
## Sniper BOT mode
## #################################################################

if [ $# -eq 0 ]
  then
    echo "[Sniper] No arguments supplied"
fi

if [ ! -z "$2" ]; then
    PROJECT_ENV="$2"  # Custom SDK name (eg. SnipAR in order to gather in on Unity3D project all packages build, per platforms)
else
    echo "[Sniper] No arguments supplied for bot actions mode"
    PROJECT_ENV="BOT_MODE" # Default output SDK name
fi

## #################################################################
## project prepare and build
## #################################################################

if [ "$2" == "ENV_MODE" ]; then
    echo "[Sniper] CMake arguments loaded..."
else
    ${SNIPER_BOTS_COMMAND}  ${PROJECT_NAME} \
                            ${PROJECT_BUILD_TYPE} \
                            ${PROJECT_VCS_URL} \
                            ${PROJECT_VCS_BRANCH} \
                            ${PROJECT_CMAKE_ARGS_FILE} \
                            ${PROJECT_CMAKE_HOME} \
                            ${PROJECT_LIBRARY_TARGET} \
                            ${PROJECT_EXECUTABLE_TARGET}
fi

## #################################################################
## project extra post-build commands
## #################################################################

## Copy output to a cache repository (eg. Hunter)
## Push output to github repository



## #################################################################
## output library integration / symbolification
## #################################################################

## Execute unit tests and re-symbolofication



## #################################################################
## project build reports and analysis
## #################################################################

## Check additional issues related to project or project forks


#
#
#
#### END ############################################################################################################################ END ####

Have a great day !

Cheers, Richard