How difficult is it to reach the internals of a PackageCompiler.jl app?
Assume that the main function only calls SomePackage.somefunction(ARGS[1])
, is it then feasible to using only the compiled artifact(s) to somehow call SomePackage.anotherfunction
?
For example, if I have been given an executable .jar
file, I think it is easy to call other methods than the main method if I just import it to a java project, and I can unzip the .jar
to see its contents. Is it similar for PackageCompiler.jl or is the sysimage more opaque?
You should always be able to load the generated sysimg into a normal Julia process (with -J
) and can then do whatever you want, no?
Sorry, I have never used PackageCompiler.jl before so I'm completely new to it.
So even a compiled "app" can be loaded as a normal image and then you have access to all the included packages?
Thanks, should have read more than just the first section :rolling_eyes:
I can't find mark resolved. Is it not available in the browser version of Zulip?
it's there for me in the browser:
image.png
DrChainsaw has marked this topic as resolved.
Last updated: Nov 06 2024 at 04:40 UTC