Search Results for "macros for mac"

Absinthe is the GraphQL toolkit for Elixir, an implementation of the GraphQL specification built to suit the language's capabilities and idiomatic style. If you're new to GraphQL, we suggest you read up a bit on GraphQL's foundational principles before you dive into Absinthe. Absinthe's functionality generally falls into two broad areas. Defines the structure of data entities and the relationships between, as well as the available queries, mutations, and subscriptions, using an elegant...

Pyexpander is a powerful macro processor based on python. Instead of simple macro replacement it offers evaluation of arbitrary python expressions and execution of python code. Pyexpander is Turing Complete.

JxMake is a Java-based, cross-platform build system primarily inspired by the syntax and features of GNU Make, Perforce Jam, and CMake. In addition, JxMake provides several capabilities not typically found in other console-based build systems, including a built-in lightweight GUI, serial console, serial plotter, multi-MCU in-system programmer, and more. Currently, JxMake's loadable libraries (build scripts) are primarily designed for non-OS MCU systems and experimental use. Full...

Currently, each babel plugin in the babel ecosystem requires that you configure it individually. This is fine for things like language features but can be a frustrating overhead for libraries that allow for compile-time code transformation as an optimization. babel-plugin-macros defines a standard interface for libraries that want to use compile-time code transformation without requiring the user to add a babel plugin to their build system (other than babel-plugin-macros, which is ideally...

Command-line/Ant-task/embeddable text file preprocessor. Macros, flow control, expressions. Recursive directory processing. Extensible in Java to display data from any data sources (as database). Can generate complete homepages (tree of HTML-s, images, etc.)

Cado is a mature code generation language that operates on standard templates with embedded macros. It is useful for generating source code and other related content (tests, docs, configuations, etc.), deriving from a common project nomenclature.

This project has useful CMake macros and modules for building scientific projects. The Modules are generalized to be used with any new and/or existing projects.

ckon is a C++ program/tool which automatically takes care of compilation, dictionary generation and linking of programs and libraries developed for data analyses within the CERN ROOT analysis framework. This includes parsing include headers to figure out which libraries the main programs need to be linked to. It uses automake/autoconf to be platform independent and GNU install compliant. In addition, m4 macros are automatically downloaded and the according compiler flags included based on a...

A collection of autoconf macros, plus an autogen.sh script that can be used with them.

Overview of pre-defined compiler macros for standards, compilers, operating systems, and hardware architectures.

The Autoconf Macro Archive provides documented and tested macros that are useful to many software writers using the autoconf tool, but too specific to be included into autoconf itself. [DISCONTINUED]

Sopi is an Ant task that instruments System.out.println() statements in place. System.out.println("Hello") becomes System.out.println("test.java, 43: " + "Hello"). It grew from a need for the Java equivalent of the C Macros __LINE__ and __FILE__.

Extended C gives Object-Oriented features such as self-referential structure pointers via macros to C, resulting in an object-oriented style. Currently tested in gcc, we hope to stabilize it for other compilers as well, including Borland & Visual Studio.

Build tracer is an application to keep track of build counts in your programming projects. No messy macros, no #defines, just add a pre-link step to this executable and it will keep track of how many times you build your projects.

When writting portable C++ CORBA code one finds that each ORB vendor has its own set of libraries, include files, caracteristics, etc. This project's goal is both: 1. to provide a set of autoconf/automake/libtool macros to support as many ORBs (C & C++)