summaryrefslogtreecommitdiff
path: root/portmidi/pm_java/README.txt
diff options
context:
space:
mode:
authorMitja Felicijan <mitja.felicijan@gmail.com>2024-10-07 19:30:56 +0200
committerMitja Felicijan <mitja.felicijan@gmail.com>2024-10-07 19:30:56 +0200
commit40a899bd6ee536eae093337bf2d0dcc8db4e46f1 (patch)
tree485ace3e6fd28b91f394efd277732651e10824d8 /portmidi/pm_java/README.txt
parent6fc4bddfdf8e056469f316c1a0fe488efbb4253a (diff)
downloadttdaw-40a899bd6ee536eae093337bf2d0dcc8db4e46f1.tar.gz
Moved example code examples folder
Diffstat (limited to 'portmidi/pm_java/README.txt')
-rw-r--r--portmidi/pm_java/README.txt62
1 files changed, 0 insertions, 62 deletions
diff --git a/portmidi/pm_java/README.txt b/portmidi/pm_java/README.txt
deleted file mode 100644
index d1e5ad5..0000000
--- a/portmidi/pm_java/README.txt
+++ /dev/null
@@ -1,62 +0,0 @@
-README.txt
-Roger B. Dannenberg
-16 Jun 2009
-updated 2021
-
-This directory implements a JNI library so that Java programs can use
-the PortMidi API. This was mainly created to implement PmDefaults, a
-program to set default input and output devices for PortMidi
-applications. Because it is rarely used, PmDefaults was dropped from
-PortMidi starting with v3. I recommend you implement per-application
-preferences and store default PortMidi device numbers for input and
-output there. (Or better yet, store device *names* since numbers can
-change if you plug in or remove USB devices.)
-
-Even without PmDefaults, a PortMidi API for Java is probably an
-improvement over other Java libraries, but there is very little MIDI
-development in Java, so I have not maintained this API. The only thing
-probably seriously wrong now is an interface to the
-Pm_CreateVirtualInput and Pm_CreateVirtualOutput functions, which are
-new additions.
-
-I will leave the code here, and if there is a demand, please either
-update it or let your needs be known. Perhaps I or someone can help.
-
-==================================================================
-
-BUILDING Java EXTERNAL LIBRARY
-
-You must have a JDK installed (Java development kit including javac
-(the Java compiler), jni.h, etc.
-
-Test java on the command line, e.g., type: javac -version
-
-Enable these options in the main CMakeLists.txt file (run CMake
-from your top-level repository directory):
- BUILD_JAVA_NATIVE_INTERFACE
-In my Ubuntu linux with jdk-15, ccmake was unable to find my JDK, so
-I have to manually set CMake variables as follows (type 't' to see
-these in ccmake):
- JAVA_AWT_INCLUDE_PATH /usr/lib/jvm/jdk-15/include
- JAVA_AWT_LIBRARY /usr/lib/jvm/jdk-15/lib
- JAVA_INCLUDE_PATH /usr/lib/jvm/jdk-15/include
- JAVA_INCLUDE_PATH2 /usr/lib/jvm/jdk-15/include
- JAVA_JVM_LIBRARY /usr/lib/jvm/jdk-15/lib
-Of course, your paths may differ.
-
-
----- old implementation notes ----
-
-For Windows, we use the free software JavaExe.exe. The copy here was
-downloaded from
-
-http://software.techrepublic.com.com/abstract.aspx?kw=javaexe&docid=767485
-
-I found this page by visiting http://software.techrepublic.com.com and
-searching in the "Software" category for "JavaExe"
-
-JavaExe works by placing the JavaExe.exe file in the directory with the
-Java application jar file and then *renaming* JavaExe.exe to the name
-of the jar file, but keeping the .exe extension. (See make.bat for this
-step.) Documentation for JavaExe can be obtained by downloading the
-whole program from the URL(s) above.