ollama/llm/llm_darwin_amd64.go

package llm

import (
	"embed"
	"syscall"
)

//go:embed build/darwin/x86_64/*/bin/*
var libEmbed embed.FS

var LlamaServerSysProcAttr = &syscall.SysProcAttr{}
Always dynamically load the llm server library This switches darwin to dynamic loading, and refactors the code now that no static linking of the library is used on any platform 2024-01-09 20:29:58 -08:00			`package llm`

			`import (`
			`"embed"`
Enable windows error dialog for subprocess startup Make sure if something goes wrong spawning the process, the user gets enough info to be able to try to self correct, or at least file a bug with details so we can fix it. Once the process starts, we immediately change back to the recommended setting to prevent the blocking dialog. This ensures if the model fails to load (OOM, unsupported model type, etc.) the process will exit quickly and we can scan the stdout/stderr of the subprocess for the reason to report via API. 2024-07-15 09:25:56 -07:00			`"syscall"`
Always dynamically load the llm server library This switches darwin to dynamic loading, and refactors the code now that no static linking of the library is used on any platform 2024-01-09 20:29:58 -08:00			`)`

Switch back to subprocessing for llama.cpp This should resolve a number of memory leak and stability defects by allowing us to isolate llama.cpp in a separate process and shutdown when idle, and gracefully restart if it has problems. This also serves as a first step to be able to run multiple copies to support multiple models concurrently. 2024-03-14 10:24:13 -07:00			`//go:embed build/darwin/x86_64//bin/`
Always dynamically load the llm server library This switches darwin to dynamic loading, and refactors the code now that no static linking of the library is used on any platform 2024-01-09 20:29:58 -08:00			`var libEmbed embed.FS`
Enable windows error dialog for subprocess startup Make sure if something goes wrong spawning the process, the user gets enough info to be able to try to self correct, or at least file a bug with details so we can fix it. Once the process starts, we immediately change back to the recommended setting to prevent the blocking dialog. This ensures if the model fails to load (OOM, unsupported model type, etc.) the process will exit quickly and we can scan the stdout/stderr of the subprocess for the reason to report via API. 2024-07-15 09:25:56 -07:00
			`var LlamaServerSysProcAttr = &syscall.SysProcAttr{}`