2021-08-27 15:45:33 +00:00
{ fetchFromGitHub
, lib
2021-10-07 10:24:36 +00:00
, Security
2021-08-27 15:45:33 +00:00
, openssl
, pkg-config
, protobuf
, rustPlatform
2021-09-10 14:37:56 +00:00
, stdenv
2021-08-27 15:45:33 +00:00
} :
2022-04-05 15:41:56 +00:00
# Updating this package will force an update for nodePackages.prisma. The
# version of prisma-engines and nodePackages.prisma must be the same for them to
# function correctly.
2021-10-13 16:38:22 +00:00
rustPlatform . buildRustPackage rec {
2021-08-27 15:45:33 +00:00
pname = " p r i s m a - e n g i n e s " ;
2022-06-28 13:27:56 +00:00
version = " 4 . 0 . 0 " ;
2021-08-27 15:45:33 +00:00
src = fetchFromGitHub {
owner = " p r i s m a " ;
repo = " p r i s m a - e n g i n e s " ;
rev = version ;
2022-06-28 13:27:56 +00:00
sha256 = " s h a 2 5 6 - T l K j A f p y g Q q 2 c 7 7 d 6 Z o M I B t W C 0 b A i M i K y g F k h 5 G r B B c = " ;
2021-08-27 15:45:33 +00:00
} ;
# Use system openssl.
OPENSSL_NO_VENDOR = 1 ;
2022-06-28 13:27:56 +00:00
cargoSha256 = " s h a 2 5 6 - / / K i s 4 l D i 3 S x e p t C C n L i / G W P j + K y a y 2 p Q b I L Y n l E k X E = " ;
2021-08-27 15:45:33 +00:00
nativeBuildInputs = [ pkg-config ] ;
2021-10-07 10:24:36 +00:00
buildInputs = [
openssl
protobuf
] ++ lib . optionals stdenv . isDarwin [ Security ] ;
2021-08-27 15:45:33 +00:00
preBuild = ''
export OPENSSL_DIR = $ { lib . getDev openssl }
treewide: use lib.getLib for OpenSSL libraries
At some point, I'd like to make another attempt at
71f1f4884b5 ("openssl: stop static binaries referencing libs"), which
was reverted in 195c7da07df. One problem with my previous attempt is
that I moved OpenSSL's libraries to a lib output, but many dependent
packages were hardcoding the out output as the location of the
libraries. This patch fixes every such case I could find in the tree.
It won't have any effect immediately, but will mean these packages
will automatically use an OpenSSL lib output if it is reintroduced in
future.
This patch should cause very few rebuilds, because it shouldn't make
any change at all to most packages I'm touching. The few rebuilds
that are introduced come from when I've changed a package builder not
to use variable names like openssl.out in scripts / substitution
patterns, which would be confusing since they don't hardcode the
output any more.
I started by making the following global replacements:
${pkgs.openssl.out}/lib -> ${lib.getLib pkgs.openssl}/lib
${openssl.out}/lib -> ${lib.getLib openssl}/lib
Then I removed the ".out" suffix when part of the argument to
lib.makeLibraryPath, since that function uses lib.getLib internally.
Then I fixed up cases where openssl was part of the -L flag to the
compiler/linker, since that unambigously is referring to libraries.
Then I manually investigated and fixed the following packages:
- pycurl
- citrix-workspace
- ppp
- wraith
- unbound
- gambit
- acl2
I'm reasonably confindent in my fixes for all of them.
For acl2, since the openssl library paths are manually provided above
anyway, I don't think openssl is required separately as a build input
at all. Removing it doesn't make a difference to the output size, the
file list, or the closure.
I've tested evaluation with the OfBorg meta checks, to protect against
introducing evaluation failures.
2022-03-25 15:33:21 +00:00
export OPENSSL_LIB_DIR = $ { lib . getLib openssl } /lib
2021-08-27 15:45:33 +00:00
export PROTOC = $ { protobuf } /bin/protoc
export PROTOC_INCLUDE = " ${ protobuf } / i n c l u d e " ;
export SQLITE_MAX_VARIABLE_NUMBER = 250000
export SQLITE_MAX_EXPR_DEPTH = 10000
'' ;
2021-09-25 11:30:22 +00:00
cargoBuildFlags = " - p q u e r y - e n g i n e - p q u e r y - e n g i n e - n o d e - a p i - p m i g r a t i o n - e n g i n e - c l i - p i n t r o s p e c t i o n - c o r e - p p r i s m a - f m t " ;
2021-08-27 15:45:33 +00:00
postInstall = ''
2021-10-13 16:38:22 +00:00
mv $ out/lib/libquery_engine $ { stdenv . hostPlatform . extensions . sharedLibrary } $ out/lib/libquery_engine.node
2021-08-27 15:45:33 +00:00
'' ;
# Tests are long to compile
doCheck = false ;
meta = with lib ; {
description = " A c o l l e c t i o n o f e n g i n e s t h a t p o w e r t h e c o r e s t a c k f o r P r i s m a " ;
homepage = " h t t p s : / / w w w . p r i s m a . i o / " ;
license = licenses . asl20 ;
2021-10-07 10:24:36 +00:00
platforms = platforms . unix ;
2022-03-26 11:33:37 +00:00
maintainers = with maintainers ; [ pamplemousse pimeys superherointj ] ;
2021-08-27 15:45:33 +00:00
} ;
}
2022-04-27 08:51:30 +00:00
### Troubleshooting
# Here's an example application using Prisma with Nix: https://github.com/pimeys/nix-prisma-example
# At example's `flake.nix` shellHook, notice the requirement of defining environment variables for prisma, it's values will show on `prisma --version`.
# Read the example's README: https://github.com/pimeys/nix-prisma-example/blob/main/README.md
# Prisma requires 2 packages, `prisma-engines` and `nodePackages.prisma`, to be at *exact* same versions.
# Certify at `package.json` that dependencies "@prisma/client" and "prisma" are equal, meaning no caret (`^`) in version.
# Configure NPM to use exact version: `npm config set save-exact=true`
# Delete `package-lock.json`, delete `node_modules` directory and run `npm install`.
# Run prisma client from `node_modules/.bin/prisma`.
# Run `./node_modules/.bin/prisma --version` and check if both prisma packages versions are equal, current platform is `linux-nixos`, and other keys equal to the prisma environment variables you defined for prisma.
# Test prisma with `generate`, `db push`, etc. It should work. If not, open an issue.