Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
P
PrivateStorageMobile
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jean-Paul Calderone
PrivateStorageMobile
Commits
6a3697e8
Commit
6a3697e8
authored
2 years ago
by
Jean-Paul Calderone
Browse files
Options
Downloads
Patches
Plain Diff
update notes
parent
c2b4f229
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
Notes.rst
+36
-0
36 additions, 0 deletions
Notes.rst
crossenv/flake.nix
+33
-0
33 additions, 0 deletions
crossenv/flake.nix
with
69 additions
and
0 deletions
Notes.rst
+
36
−
0
View file @
6a3697e8
...
...
@@ -4,6 +4,29 @@
* Build an app that can read magic-folders and download linked files
* Build libchallenge_bypass_ristretto for armv7a and aarch64 Android
* nixpkgs *used to* use "crates-io.nix" which was quite friendly to cross-compilation!
But it got thrown in the trash and now you are directed to naersk or crate2nix.
* cross-compilation with crate2nix expressions is not straightforward
Does it work at all, for anything?
Who knows.
There's a ticket open.
I haven't yet figured out how to make it go.
* naersk looks super easy to use!
But does it support cross-compilation?
It is not clear.
(Naive?) Attempts to do so on nixpkgs master@HEAD fail with infinite recursion errors.
On nixos-22.05 with some patches applied ... maybe it will work?
(As of 2022-12-05 16:04, build is still running)
* Either way we need to preserve our postInstall step to get the .h and .pc files
* Build an app that runs a Haskell Tahoe-LAFS implementation on Android
* Reflex-FRP / Obsidian Systems Obelisk?
...
...
@@ -180,8 +203,21 @@
(by inspection with builtins.trace)
* python-cryptography
* cffi-based projects seem to be tricky!
* python-challenge-bypass-ristretto
* crossenv can do it!
See crossenv subdirectory.
* However, crossenv can't do python-challenge-bypass-ristretto
or python-cryptography.
These seem to have cffi as a build-time dependency.
Cross-env gives the build pip env the host cffi .so so it fails.
* Integrate a Python Tahoe-LAFS runtime with a GUI
* Build a GUI
This diff is collapsed.
Click to expand it.
crossenv/flake.nix
0 → 100644
+
33
−
0
View file @
6a3697e8
{
inputs
.
nixpkgs
.
url
=
"github:NixOS/nixpkgs?rev=3d58e3a31ee55554fe26650bb59db7d6d0e97625"
;
outputs
=
{
self
,
nixpkgs
}:
let
native-pkgs
=
import
nixpkgs
{
system
=
"x86_64-linux"
;
allowUnfree
=
true
;
android_sdk
.
accept_license
=
true
;
};
cross-pkgs
=
native-pkgs
.
pkgsCross
.
aarch64-android
;
platformVersion
=
"31"
;
cmakeVersion
=
"3.10.2"
;
buildToolsVersion
=
"31.0.0"
;
# Check out pkgs/development/mobile/androidenv/repo.json for
# nixpkgs-supported versions.
ndkVersion
=
"23.0.7123448-rc1"
;
androidComposition
=
native-pkgs
.
callPackage
../android.nix
{
inherit
cmakeVersion
buildToolsVersion
platformVersion
ndkVersion
;
};
in
{
devShells
.
x86_64-linux
.
default
=
native-pkgs
.
mkShell
rec
{
BUILD_PYTHON
=
"
${
native-pkgs
.
python3Minimal
}
/bin/python"
;
HOST_PYTHON
=
"
${
cross-pkgs
.
python3Minimal
}
/bin/python"
;
ANDROIDSDK
=
"
${
androidComposition
.
androidsdk
}
/libexec/android-sdk"
;
ANDROIDNDK
=
"
${
ANDROIDSDK
}
/ndk-bundle"
;
shellHook
=
''
export PATH="$(echo "$ANDROIDSDK/cmake/
${
cmakeVersion
}
".*/bin):$PATH"
''
;
};
};
}
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment