Dstep

A tool for converting C and Objective-C headers to D modules
Alternatives To Dstep
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Include What You Use3,522
3 days ago2May 05, 2022252otherC++
A tool for use with clang to analyze #includes in C and C++ source files
Checkedc3,151
a year ago61otherC
Checked C is an extension to C that lets programmers write C code that is guaranteed by the compiler to be type-safe. The goal is to let people easily make their existing C code type-safe and eliminate entire classes of errors. Checked C does not address use-after-free errors. This repo has a wiki for Checked C, sample code, the specification, and test code.
Glow3,045
21 hours ago391apache-2.0C++
Compiler for Neural Network hardware accelerators
Cling3,0021a month ago6October 29, 2022180otherC++
The cling C++ interpreter
Clang2,753
3 years agoapache-2.0C++
Mirror kept for legacy. Moved to https://github.com/llvm/llvm-project
Cppinsights2,458
16 hours ago18mitC++
C++ Insights - See your source code with the eyes of a compiler
Qt Creator2,176
13 hours ago6otherC++
A cross-platform Qt IDE
Souper2,004
10 days ago92apache-2.0C++
A superoptimizer for LLVM IR
Codechecker1,942215 hours ago63March 05, 2021339apache-2.0Python
CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy
Libbpf1,599
11 days ago1July 27, 202212otherC
Automated upstream mirror for libbpf stand-alone build.
Alternatives To Dstep
Select To Compare


Alternative Project Comparisons
Readme

DStep

DStep is a tool for automatically generating D bindings for C and Objective-C libraries. This is implemented by processing C or Objective-C header files and output D modules. DStep uses the Clang compiler as a library (libclang) to process the header files.

Download

For the latest release see: releases/latest.

Pre-compiled binaries are available for macOS and Linux as 64 bit binaries and Windows as 32 and 64 bit binaries. The Linux binaries are completely statically linked and should work on all distros. The macOS binaries are statically linked against libclang requires no other dependencies than the system libraries. They should work on macOS Mavericks (10.9) and later. The Windows binaries require to install libclang. See the releases section.

Alternatively install via Dub

License

The source code is available under the Boost Software License 1.0

Building

Posix

Requirements

Building

  1. Install all requirements, see above

  2. Clone the repository by running:

     $ git clone https://github.com/jacob-carlborg/dstep
    
  3. Run dub build

A configuration script will try to automatically locate libclang by looking through a couple of default search paths. If libclang is not found in any of the default paths, please manually invoke the configuration script and specify the path to where libclang is installed using the --llvm-path flag.

$ ./configure --llvm-path /usr/lib/llvm-4.0

Windows

Requirements

Building

  1. Install all requirements, see above

  2. Clone the repository by running:

     $ git clone git://github.com/jacob-carlborg/dstep.git
    
  3. Run dub build --arch=x86_mscoff --build=release to build 32-bit version

  4. Run dub build --arch=x86_64 --build=release to build 64-bit version

Remarks

Building 32-bit version requires a 32-bit variant of the Visual Studio toolchain to be present in PATH. The same for 64-bit. Remember to specify --arch=x86_mscoff when building 32-bit version. The architecture specification is mandatory as with the default architecture or --arch=x86 dub will try to use unsupported OPTLINK linker. OPTLINK linker requires unsupported version of libclang binaries. Remember to install LLVM to its default installation path and to add its binaries to the PATH environmental variable (otherwise you may need to change dub.json). When the program compiles under Windows but crashes at start, make sure an appropriate version of libclang.dll is available for DStep (you can validate it easily by copying dll to the directory with DStep). Here you can find more information on the topic.

Usage

$ dstep Foo.h -o Foo.d

For translating Objective-C headers add the -ObjC flag.

$ dstep Foo.h -o Foo.d -ObjC

For translating multiple files at once, simply pass all the files to dstep. In this case though, -o (if given) would point to output directory name. The directory will be created if it doesn't exist.

$ dstep Foo1.h Foo2.h Foo3.h .... FooN.h -o ./outputDirectory/

Use -h for usage information. Any flags recognized by Clang can be used.

Limitations/Known issues

  • Supports translating some of the preprocessor, like: #define for simple constants, function like macros and the token concatenation operator (##)

  • Doesn't translate #include to import. Imports for a few standard C headers are added automatically

  • Doesn't translate C++ at all

  • Umbrella headers. Some headers just serve to include other headers. If these other headers contain some form of protection, like #error, to be included directly this can cause problems for DStep

  • Some headers are designed to always be included together with other header files. These headers may very well use symbols from other header files without including them itself. Since DStep is designed to convert header files one-by-one this doesn't work. There are two workarounds for this:

    1. Add #include-directives for the header files the header file is actually using
    2. Use the -include <file> flag available in Clang to indicate the given <file> should be processed before the file that should be translated. DStep accepts all flags Clang accepts
Popular Llvm Projects
Popular Clang Projects
Popular Compilers Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
C
Objective C
Dlang
Llvm
Clang
Libclang