forked from genericworkflownodes/GenericKnimeNodes
-
Notifications
You must be signed in to change notification settings - Fork 0
/
payload.README
49 lines (33 loc) · 1.55 KB
/
payload.README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
The plugins built using the GenericKnimeNodes functionality need the binary programs
executed by each node to reside in a payload directory containing special zip archives.
For each target platform (mac, lnx, win) there has to be a zip archive.
For each supported platform the payload directory should contain two files :
- binaries_<platform>_<wordsize>.ini - a ini file containing needed environment variables
- binaries_<platform>_<wordsize>.zip - a zip file containing a bin folder with executable
binaries, a lib folder with needed libraries and an optional data directory
Where <platform> is either: win, mac or lnx and <wordsize> 32 or 64.
For Linux 64 bit systems as target a ini-file named
binaries_lnx_64.ini
might look like :
LD_LIBRARY_PATH=$ROOT/lib/
DATA_PATH=$ROOT/data/
The corresponding binaries_lnx_64.zip content would look like this :
bin/
|
+--- foo
|
+---- bar
lib/
|
+---- baz.so
data/
|
+---- data.dat
where foo and bar are executable binaries placed in the bin directory, baz.so is
a needed library that is placed in the lib directory. The data directory contains
a file with some addtional data foo or bar might need during execution.
So fo each target OS and word size you need to prepare a corresponding pair of files
(binaries_<platform>_<wordsize>.ini,binaries_<platform>_<wordsize>.zip) that all reside
in a payload directory. The contents of the whole payload directory will be packaged
into the final plugin jar and (depending on the execution platform) will be extracted
upon execution on a host system.