For example if you had a folder called jre1.8.0_112 containing the Oracle JRE you might have a part such as:. Or by adding a part containing the Oracle JRE, unpacked and put in a relavent place. In this instance you should bundle the relevant jvm for your application. When the snap is launched, the path is setup correctly for it to find binaries located in $SNAP/bin, however it won't see things outside the snap, like for example (in your case) the java runtime. There are envionment variables which point to the most important ones. Strictly confined snaps are typically can't 'see' folders outside the snap itself, and some other locations. P.D: Am I pointing correctly to my executable jar? I also tried adding the route to the /prime/jar/ folder but nothing. When do you need to point to a "executable file" and when is not needed, just a word?.
When do you need to write just the word in command and when do you need to write the mand-word?.sh and others just need to write a name for running the snap? Why the bin folder in "command"? is autogenerated by snapcraft? is it mandatory in some specific cases?.Going further than solving my problem (which it'd great), I have some questions: yaml trying to reach and execute the jar who runs my daemon: apps:Ĭommand: java -cp $SNAP/basic-project-0.0.1-SNAPSHOT.jar es.daemon.Daemontestīut when type "daemon-test" or "name-snap.daemon-test" I get the "command not found" prompt. I understand they are pointing at the folder where the executable file is located, so I did the same with my. Some of the tutorials just use "command: example" and run the snap typing "example", other use "command: bin/example" or even "command: bin/example.sh". yaml for the snaps works, or better said, how I can invoke the snap. After reading the " building snap tutorial" and checking the documentation, other tutorials and some examples, I'm still confused about how the command section in the.
0 kommentar(er)
