-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initialization Error in PackageCompiler app on Windows when relocating #371
Comments
Just want to confirm that you're running |
Yes, I'm running I did the same thing for the Ubuntu test (ubuntu to ubuntu) that passed. |
I believe this may have been a corner case that has just slipped through the cracks until now. Typically the directory creation is handled when the package is built. On Windows however we do this directory creation check during package initialization. I already have a fix for that but I'm doubtful that will fix everything here (if the directory doesn't exist then the required file isn't included in the compiled package). If you want to give it a try you can using the |
Thanks! I'll give it a try and let you know. |
There seems to be an initialization error in applications generated through
PackageCompiler.jl
usingTimeZones.jl
as a dependency on Windows when relocating to another computer (i.e. sharing a quick CLI app with a not-yet-converted-to-glorious-julia-prog colleague)Consider the following:
Foo module
Generating the app with
PackageCompiler v2.0.4
andTimeZones v1.7.0
(n.b. I have not tested with lower versions of each pkg)I initially thought the error was because of not including lazy artifacts, but I've tested both ways to make sure with same results
Error stacktrace
I've tested this on Windows 10 with julia
1.6.4
and1.7.1
(to check if my recent Julia version update was the culprit) with the same error.The error does not seem to occur on Linux (tested wih
Ubuntu 20.04.3 LTS
+julia 1.7.1
)I'm not too savvy with the internals of TimeZones/PackageCompiler (
TimeZones.jl
is actually a dep of a dep for the app I was trying to share) so if I was to venture a guess I'd say, based on the init error occurring on trying to create a directory with a path from the build machine, that it might be related to# 357? edit: wrong guess it seems, de-linking the issuesI'm a little dubious that in the 2 years since eb1881a I'd be the first person to hit this problem (but maybe something changed in
PackageCompiler
since then.. ) -- to be taken with a grain of salt.Please let me know if you need further clarifications, I'll be glad to help.
With regards,
The text was updated successfully, but these errors were encountered: