From e2505d1d9e2e49554057a8cd5fb71b0ac0e3ba63 Mon Sep 17 00:00:00 2001 From: Jakob Odersky Date: Sun, 6 Dec 2015 17:03:08 -0800 Subject: Use separate project for native libraries --- README.md | 16 ++-------------- 1 file changed, 2 insertions(+), 14 deletions(-) (limited to 'README.md') diff --git a/README.md b/README.md index d861fec..6fd8d55 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,2 @@ -# Definitions -- Native binaries: artifacts such as libraries and executables that are platform dependent, typically C/C++ projects - -# Goals: - -## Wrapper -- Native binaries are compiled with another build tool, such as Make, Autotools or CMake -- Provides a "Native" configuration with most standard sbt tasks. -Why not provide separate tasks, like nativeCompile and nativeTest? individual tasks don't map, that's the whole idea to use a wrapper - -## JNI -- Generate JNI headers - - +# SBT-JNI +Making JNI tolerable. -- cgit v1.2.3