2021-10-28 10:46:45 +02:00
|
|
|
[package]
|
|
|
|
|
name = "anki"
|
|
|
|
|
version = "0.1.0"
|
|
|
|
|
build = "build.rs"
|
2021-11-18 11:51:10 +01:00
|
|
|
edition = "2021"
|
2021-10-28 10:46:45 +02:00
|
|
|
|
2021-10-28 10:57:21 +02:00
|
|
|
[target.'cfg(windows)'.dependencies]
|
|
|
|
|
winapi = {version = "0.3", features = ["wincon"]}
|
|
|
|
|
libc = "0.2"
|
|
|
|
|
libc-stdhandle = "=0.1.0"
|
2021-10-28 10:46:45 +02:00
|
|
|
|
|
|
|
|
[dependencies.pyembed]
|
|
|
|
|
git = "https://github.com/ankitects/PyOxidizer.git"
|
updates to the build process and binary bundles
All platforms:
- rename scripts/ to tools/: Bazelisk expects to find its wrapper script
(used by the Mac changes below) in tools/. Rather than have a separate
scripts/ and tools/, it's simpler to just move everything into tools/.
- wheel outputs and binary bundles now go into .bazel/out/dist. While
not technically Bazel build products, doing it this way ensures they get
cleaned up when 'bazel clean' is run, and it keeps them out of the source
folder.
- update to the latest Bazel
Windows changes:
- bazel.bat has been removed, and tools\setup-env.bat has been added.
Other scripts like .\run.bat will automatically call it to set up the
environment.
- because Bazel is now on the path, you can 'bazel test ...' from any
folder, instead of having to do \anki\bazel.
- the bat files can handle being called from any working directory,
so things like running "\anki\tools\python" from c:\ will work.
- build installer as part of bundling process
Mac changes:
- `arch -arch x86_64 bazel ...` will now automatically use a different
build root, so that it is cheap to switch back and forth between archs
on a new Mac.
- tools/run-qt* will now automatically use Rosetta
- disable jemalloc in Mac x86 build for now, as it won't build under
Rosetta (perhaps due to its build scripts using $host_cpu instead of
$target_cpu)
- create app bundle as part of bundling process
Linux changes:
- remove arm64 orjson workaround in Linux bundle, as without a
readily-available, relatively distro-agonstic PyQt/Qt build
we can use, the arm64 Linux bundle is of very limited usefulness.
- update Docker files for release build
- include fcitx5 in both the qt5 and qt6 bundles
- create tarballs as part of the bundling process
2022-01-30 01:50:14 +01:00
|
|
|
# when changing this, pyoxidizer in /repos.bzl needs to be updated as well
|
2021-12-08 09:11:25 +01:00
|
|
|
rev = "eb26dd7cd1290de6503869f3d719eabcec45e139"
|
2021-10-28 10:46:45 +02:00
|
|
|
default-features = false
|
|
|
|
|
|
|
|
|
|
[dependencies.jemallocator]
|
|
|
|
|
version = "0.3"
|
|
|
|
|
optional = true
|
|
|
|
|
|
|
|
|
|
[dependencies.mimalloc]
|
|
|
|
|
version = "0.1"
|
|
|
|
|
optional = true
|
|
|
|
|
features = ["local_dynamic_tls", "override", "secure"]
|
|
|
|
|
|
|
|
|
|
[dependencies.snmalloc-rs]
|
|
|
|
|
version = "0.2"
|
|
|
|
|
optional = true
|
|
|
|
|
|
|
|
|
|
[build-dependencies]
|
|
|
|
|
embed-resource = "1.6"
|
|
|
|
|
|
|
|
|
|
[features]
|
|
|
|
|
default = ["build-mode-standalone"]
|
|
|
|
|
|
|
|
|
|
global-allocator-jemalloc = ["jemallocator"]
|
|
|
|
|
global-allocator-mimalloc = ["mimalloc"]
|
|
|
|
|
global-allocator-snmalloc = ["snmalloc-rs"]
|
|
|
|
|
|
|
|
|
|
allocator-jemalloc = ["pyembed/allocator-jemalloc"]
|
|
|
|
|
allocator-mimalloc = ["pyembed/allocator-mimalloc"]
|
|
|
|
|
allocator-snmalloc = ["pyembed/allocator-snmalloc"]
|
|
|
|
|
|
|
|
|
|
# Build this crate in isolation, without using PyOxidizer.
|
|
|
|
|
build-mode-standalone = []
|
|
|
|
|
|
|
|
|
|
# Build this crate by executing a `pyoxidizer` executable to build
|
|
|
|
|
# required artifacts.
|
|
|
|
|
build-mode-pyoxidizer-exe = []
|
|
|
|
|
|
|
|
|
|
# Build this crate by reusing artifacts generated by `pyoxidizer` out-of-band.
|
|
|
|
|
# In this mode, the PYOXIDIZER_ARTIFACT_DIR environment variable can refer
|
|
|
|
|
# to the directory containing build artifacts produced by `pyoxidizer`. If not
|
|
|
|
|
# set, OUT_DIR will be used.
|
|
|
|
|
build-mode-prebuilt-artifacts = []
|