Skip to content
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

Precompilation fails on 0.1.2 #16

Closed
Seelengrab opened this issue Apr 30, 2021 · 9 comments
Closed

Precompilation fails on 0.1.2 #16

Seelengrab opened this issue Apr 30, 2021 · 9 comments

Comments

@Seelengrab
Copy link
Contributor

Error log
Vulkan [9f14b124-c50e-4008-a7d4-969b3a6cd68a]

ERROR: LoadError: LoadError: UndefVarError: VkAccelerationStructureVersionKHR not defined
Stacktrace:
  [1] top-level scope
    @ ~\.julia\packages\Vulkan\Ek6Ym\generated\vulkan_wrapper.jl:718
  [2] include(mod::Module, _path::String)
    @ Base .\Base.jl:386
  [3] include(x::String)
    @ Vulkan ~\.julia\packages\Vulkan\Ek6Ym\src\Vulkan.jl:1
  [4] top-level scope
    @ ~\.julia\packages\Vulkan\Ek6Ym\src\Vulkan.jl:37
  [5] include
    @ .\Base.jl:386 [inlined]
  [6] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concre
deps::Vector{Pair{Base.PkgId, UInt64}}, source::Nothing)
    @ Base .\loading.jl:1213
  [7] top-level scope
    @ none:1
  [8] eval
    @ .\boot.jl:360 [inlined]
  [9] eval(x::Expr)
    @ Base.MainInclude .\client.jl:446
 [10] top-level scope
    @ none:1
in expression starting at ~\.julia\packages\Vulkan\Ek6Ym\generated\vulkan_wrapper.jl:718
in expression starting at ~\.julia\packages\Vulkan\Ek6Ym\src\Vulkan.jl:1

Stacktrace:
 [1] pkgerror(msg::String)
   @ Pkg.Types C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\Types.jl:55
 [2] precompile(ctx::Pkg.Types.Context; internal_call::Bool, strict::Bool, kwargs::Base.Iterators.Pairs{Union{}, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
   @ Pkg.API C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\API.jl:1244
 [3] precompile
   @ C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\API.jl:920 [inlined]
 [4] #precompile#196
   @ C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\API.jl:918 [inlined]
 [5] precompile()
   @ Pkg.API C:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.6\Pkg\src\API.jl:918
 [6] top-level scope
   @ REPL[5]:1

Short version:

UndefVarError: VkAccelerationStructureVersionKHR not defined at Vulkan\Ek6Ym\generated\vulkan_wrapper.jl:718. Is this from VulkanCore? Would this need a new version/update the dependency as well?

@Seelengrab
Copy link
Contributor Author

Ok, this is weird - even an explicit downgrade to 0.1.1 doesn't seem to fix this

@serenity4
Copy link
Member

Indeed, VulkanCore does not use semantic versioning (to be in line with Vulkan versions) and has been updated yesterday. It should be good on master now (locked the version for VulkanCore). Tagging a new release. After that I'll update the repo to a breaking 0.2.0 version with changes not yet pushed with the latest VulkanCore.

@serenity4
Copy link
Member

serenity4 commented Apr 30, 2021

@JuliaRegistrator register()

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/35706

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.3 -m "<description of version>" 6a623c8f93a1854ddff7334db49f281b109db84b
git push origin v0.1.3

@JuliaRegistrator
Copy link

Error while trying to register: Unexpected error in registration

@serenity4
Copy link
Member

Huuh, the registry PR looks fine, let's wait a bit and see if whatever problem goes away

@Seelengrab
Copy link
Contributor Author

The PR exists 🤔

@serenity4
Copy link
Member

It's now fixed. Thanks for reporting.

@Seelengrab
Copy link
Contributor Author

Seelengrab commented Apr 30, 2021

Yep, I can confirm it works! Same goes for the ExtensionProperties thing, the names are correct now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants