# In reply to @arnetheduck "what I mean is": You likely know more on this than I
# do or when a change happened, I think a change to the nimblepaths in the
# nim.cfg file may be screwing with building nlvm.
@if not windows:
  nimblepath="/opt/nimble/pkgs2/"
  nimblepath="/opt/nimble/pkgs/"
@else:
  # TODO:
@end
# nimblepath="$home/.nimble/pkgs2/" # <-- The evil line
nimblepath="$home/.nimble/pkgs/"

# Leaving that commented in with packages installed leads to error messages where
# it complains about various packages having invalid package names (can't copy
# paste because the error is no longer in my terminal and I kinda don't want to
# rebuild nlvm again)