-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build system dependencies #3
Comments
Also:
Should be from PIP, not from the distro repo, as the distro repo is outdated and causes the |
This is fixed in the latest MXE version but since I was having trouble, I didn't attempt to even migrate it in yet. However, there's also a dependency issue with the official MXE too... You need PCRE's dev packages which for some reason is NOT included in the index pages. |
Aaah IC. Linking to issue #2. |
Sadly this actually does not work correctly in our current repository version when using Ubuntu 22.04. This version of MXE expects |
However, it does seem they moved to Python 3 in the new version, thankfully. |
Ouch, nice of them. How much does Python3 break? |
If I'm correct, maybe... 2 or 3 packages? I don't remember. Probably easily fixable, but if I remember correctly they were all meson packages instead of CMake packages. |
Then I'll go with python3 for now until all |
Good with me. I've got latest MXE going on my system now but likely won't do too much today. |
OpenSSL for host CMake build. Goodness. Do we need it, given that mxe builds are networkless by policy? |
What!? 🤦 |
The reason for CMake to include OpenSSL is that it can retrieve dependencies over network. |
|
blas/lapack need cross-compiling |
I stand corrected — it's present in mingw (but doesn't like |
SUSE's current dependency status (even after installing needed libraries on MXE's page): Missing dependencies - Broken dependencies (no providers) - Will update this comment as I find more (if I do, anyway). |
After accidentally nuking my guest drive (sounds funny, but silent wipe of the Linux installation when physical paths change is a WSL feature), I used it as an opportunity to verify the build bootstrapping process. Here is what I found.
My distro is Ubuntu 20.04. My system already had
git
,gcc
andpython3-pip
.My initial
make
output was:I got most of the dependencies installed w/
sudo apt install
by using the names from the list as literal package names. However, there were a few exceptions:gdk-pixbuf-csource
is provided bylibgtk2.0-dev
libtool
is provided bylibtool-bin
andlibtoolize
is provided bylibtool
intltoolize
seems to be silently provided byintltool
7za
is provided byp7zip-full
(simplyp7zip
isn't enough)Also
python
was not listed as a requirement. I had to installpython3
andpython-is-python3
.We may want to update docs/index.html (I can do that). I propose to make those note distro-specific and covering at least major Ubuntu LTS distros; others can add theirs.
The text was updated successfully, but these errors were encountered: