metacritical

(ns core
  (:gen-class))

(assembly-load-from "./extern/OpenTK/lib/net20/OpenTK.dll")

(defn -main[]
  (Console/WriteLine "Starting OpenTK Window."))

metacritical

(ns core
  (:gen-class))

(import [System])

(defn -main[]
  (System.Console/WriteLine "Hi World"))

metacritical

#!/usr/local/bin/bash

runtime="mono"
cljcomp=$CLOJURE_LOAD_PATH/Clojure.Compile.exe

compile(){
  CLOJURE_COMPILE_PATH=build/ $runtime $cljcomp core
}

link_dlls(){

metacritical

using UnityEngine;

public class BoidBehaviour : MonoBehaviour
{
	void Update()
	{
		Boids.Core.update(transform);
	}
}

metacritical

>> mono all/net40/Clojure.Main.exe 

Unhandled Exception:
System.TypeInitializationException: The type initializer for 'Clojure.CljMain' threw an exception. ---> System.TypeInitializationException: The type initializer for 'clojure.lang.RT' threw an exception. ---> System.IO.FileNotFoundException: Invalid Image
  at (wrapper managed-to-native) System.Reflection.Assembly.LoadFrom(string,bool,System.Threading.StackCrawlMark&)
  at System.Reflection.Assembly.LoadFrom (System.String assemblyFile) [0x00002] in <f7cedb26ce694cd281e4450870c6fe49>:0 
  at clojure.lang.RT.DoInit () [0x0000a] in <814990e2d98549148927c9ed5c97f15e>:0 
  at clojure.lang.RT..cctor () [0x01f89] in <814990e2d98549148927c9ed5c97f15e>:0 
   --- End of inner exception stack trace ---
  at Clojure.CljMain..cctor () [0x0000f] in <f5aa122c398747a0aa41452d219b2965>:0 

metacritical

#!/usr/bin/env bash

# Version = 1.9.0.397

set -e

function join { local d=$1; shift; echo -n "$1"; shift; printf "%s" "${@/#/$d}"; }

# Extract opts
print_classpath=false

metacritical

Recent improvements to the ClojureScript compiler have greatly simplified setting up development versus production outputs.

This example uses Figwheel as something that you want to exclude for production, but the pattern is general.

With this simple setup you only need one html file/view and it will work for developement and production.

metacritical

Using JavaScript Libraries from ClojureScript

Using JavaScript libraries from ClojureScript involves two distinct concerns:

1. Packaging the code and delivering it to the browser
2. Making ClojureScript code that accesses JavaScript libraries safe for advanced optimization

Right now, the only single tool that solves these probems reliably, optimally, and with minimal configuration is shadow-cljs, and so that is what I favor. In paricular, shadow-cljs lets you install npm modules using npm or yarn and uses the resulting package.json to bundle external dependencies. Below I describe why, what alternatives there are, and what solutions I disfavor at this time.

Packaging and Delivering Code

metacritical

#include <iostream>
#include <cstdint>
#include <string>

#include "llvm/ExecutionEngine/JIT.h"
#include "llvm/IR/IRBuilder.h"
#include "llvm/IR/Module.h"
#include "llvm/PassManager.h"
#include "llvm/Support/TargetSelect.h"
#include "llvm/Analysis/Verifier.h"

metacritical

CLang -> llvm

• clang -S -emit-llvm program.c

llvm -> assembly

• llc program.ll -o program.s

Evaluate llvm bit code

• lli struct.ll

Make So files from C in clang

• clang -O3 -dynamiclib -undefined dynamic_lookup runtime.c program.s -o program.so