Skip to content

COMPILE.md

Latest commit

 

History

History
63 lines (43 loc) · 1.72 KB

COMPILE.md

File metadata and controls

63 lines (43 loc) · 1.72 KB

Building FastSpider from Source

Prerequisites

  • JDK 17+ — Download
  • Maven 3.9+ — Download
  • Visual Studio 2022 — Community/Professional/Enterprise/BuildTools

Quick Build

# 1. Build native DLL first (Windows)
compile.bat

# 2. Build JAR
mvn clean package -DskipTests

Build Commands

Command Purpose
compile.bat Build native DLL (Windows)
mvn clean compile Compile Java only
mvn clean package Build FatJAR with DLL embedded
mvn test Run unit tests

Native DLL Build

The compile.bat script:

  • Auto-detects Visual Studio 2019/2022
  • Auto-detects JAVA_HOME
  • Uses native\fastspider.def for JNI exports
  • Outputs to build\fastspider.dll

The Maven pom.xml will automatically pick up build\fastspider.dll and bundle it inside the JAR.

JNI Exports (.def File)

When using JNI, you MUST export your native functions in the native\fastspider.def file:

LIBRARY fastspider
EXPORTS
    Java_fastspider_FastSpider_doSomethingNative

Important: Function names must match Java's expected format:

  • Pattern: Java_packagename_Classname_methodname

Without the .def file, JNI methods won't be exported and you'll get UnsatisfiedLinkError.

Troubleshooting

"Cannot find DLL" — Run compile.bat first

"UnsatisfiedLinkError" — Common causes:

  1. DLL built but not included in JAR (check build/ folder).
  2. JNI exports missing — Verify .def file.
  3. Wrong function name — Must match Java_package_Class_method exactly.

"Java version mismatch" — Ensure JDK 17+ is installed and JAVA_HOME is set.