Closed daneov closed 1 year ago
I haven't been able to get updates to nixpkgs or mach-nix to work either. Also see #10.
I'm not sure what to do in general with the IDF Python dependencies. The current options I can think of are:
shell.nix
unchanged for reference, most likely won't work for IDF as-is but can serve as a starting point for exploring this:{ pkgs ? import <nixpkgs> { } }:
with pkgs;
mkShell rec {
name = "invoke-ai-pip-shell";
venvDir = "invokeai";
buildInputs = [
python310Packages.python
python310Packages.venvShellHook
];
LD_LIBRARY_PATH = lib.makeLibraryPath [
stdenv.cc.cc.lib
cudaPackages.cudatoolkit
cudaPackages.cudnn
libGL
glib
] + ":/run/opengl-driver/lib";
postVenvCreation = ''
unset SOURCE_DATE_EPOCH
ln -sf environments-and-requirements/requirements-lin-cuda.txt requirements.txt
pip install -r requirements.txt
'';
postShellHook = ''
# allow pip to install wheels
unset SOURCE_DATE_EPOCH
export INVOKEAI_ROOT=~/invokeai
echo 'Run: invoke.py --web --host 0.0.0.0'
'';
}
I'm making this the master issue for all the newer nixpkgs/mach-nix/Python environment problems.
To consider: using constraints files for Python package versions - see https://github.com/mirrexagon/nixpkgs-esp-dev/pull/15#issuecomment-1604016511
The issue with this is they might change under us and won't have a stable hash.
I manually packaged the required Python packages that weren't already in nixpkgs, instead of using mach-nix - it should work with recent nixpkgs now.
@mirrexagon: I'd like to reporting that
nix-shell shells/esp32-idf.nix
does not seem to workSteps performed:
Output:
Environment information:
I tried changing the
overlay.nix
by upgrading the db, but I must be doing something wrong: