[Bug] Make sure to build avante (missing avante_templates) #474
Comments
|
do you have cargo? |
|
Getting the same error on macOS Sonoma. cargo 1.80.1. |
|
Same. I have cargo. Linux manjaro. |
|
can you check If it compiled binary? Otherwise you can try installing from prebuilt (will require you to setup GITHUB_TOKEN) |
|
@aarnphm this is caused by build.sh checking for |
|
Output of After installing the We should need to investigate why it is not possible to compile the source files with I also deleted the |
|
Those are the scopes I selected when generating the GitHub token:
|
|
On my setup, the
where This is the result:
I had So I did and now I have I finally deleted again the Warning The build process took around one minute on a laptop. Also, this is the actual param (
[string]$Version = "luajit"
)
$BuildDir = "build"
$BuildFromSource = $true
function Build-FromSource($feature) {
if (-not (Test-Path $BuildDir)) {
New-Item -ItemType Directory -Path $BuildDir | Out-Null
}
cargo build --release --features=$feature
$targetTokenizerFile = "avante_tokenizers.dll"
$targetTemplatesFile = "avante_templates.dll"
Copy-Item (Join-Path "target\release\libavante_tokenizers.dll") (Join-Path $BuildDir $targetTokenizerFile)
Copy-Item (Join-Path "target\release\libavante_templates.dll") (Join-Path $BuildDir $targetTemplatesFile)
Remove-Item -Recurse -Force "target"
}
function Main {
Set-Location $PSScriptRoot
Write-Host "Building for $Version..."
Build-FromSource $Version
Write-Host "Completed!"
}
# Run the main function
MainThe problem is that once the build is finished, the two
but the script expects them to be named:
So, after manually copying the two |
|
I have macos (m chip). I was assuming that the build process happened at installation time of the plugin but maybe I am wrong. let me know if you need any additional info. |
|
I have a working setup now by:
This required the System is a MacOS M chip |
|
It is unreasonable for the installation script to depend on |
|
i think it works now.. |
|
I think it should be working normally now. Everyone can try reinstalling the latest version. |
|
this is what i get from lazynvim i removed avante.nvim dir and tried reinstalling |
|
@pidgeon777 Manually execute this command to see what the return value is: curl -s https://api.github.com/repos/yetone/avante.nvim/releases/latest | grep browser_download_url | cut -d '"' -f 4 |
Did you also encounter errors during the installation? |
Yes. the build script(build.sh) doesn't run well. |
Got it! Thank you for pointing out the issue! |
|
@ohseunghyeon I have already fixed this issue in the latest version. Can you try again? |
|
@yetone it works. thanks |
I'm on Windows, I installed Still, after removing the |
|
At this point, it seems that there are differences in how file paths (and build scripts) are managed differently by the plugin in Unix and Windows environments. I have created an issue regarding the handling of file paths, as it seems there is a problem specifically in the Windows version: In the meantime, it might be worth re-opening the current issue, as the problem appears to be unresolved on Windows. Finally, I added some more notes here: |
|
The Windows build script is still on the way: #483 |
|
@pidgeon777 Hi please try on the latest. Windows build script is now available. |
On Windows it succeded, the following files have been created: Still, this problem persists: making it not possible to run |
It is now solved. |
|
I am on rocky linux and installed the latest avante, but it has the same problem, please let me know if you need any info. Thanks. |
After running
:AvanteAsk, and submitting the form, the following error is thrown:My config:
nvimversion:Os is Windows 11 Pro.
The text was updated successfully, but these errors were encountered: