-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add package: gn #7290
Add package: gn #7290
Conversation
Its not picking up the correct linker
Notice Same problem for other archs EDIT: The gn gen.py was correct, it choose the correct ld. I have disabled building of gn_unittests which is basically unit tests which are useless to build (especially on CI) |
The compiled Also while building Node.js 16, v8 seems to compile for wrong arch, so having shared v8 makes sense. See suhan-paradkar#8 @xeffyr I need your approval before working on this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure you have checked how termux_setup_golang
or termux_setup_cmake
work and adjust termux_setup_gn
accordingly.
Specifically:
- Need integrity check of downloaded tarball. No matter whether it has been downloaded and checked previously. You need to verify it always.
- Do not re-install gn if it was already installed.
Fails at
Possibly you need to add |
It requires libicu now?? |
It requires icu for i18n support |
ig |
I got it why v8 fails with shared libicu. libicu is missing pkg configs, I will push the fix soon. And I got v8 building for x86_64. aarch64 build is going on. If it passes, I will add patches for v8 which will be stealed from nodejs v8 patches |
Well.. 32 bit CPUs are facing few strange problems with gn.. |
Probably that's due to some variables defined in Will try unsetting all of them after CI for aarch64 and x86_64 pass |
Same about x86_64 too...
|
Now, that I have revised libicu to include pkg-config, I can confirm that V8 is looking for icu-i18n.pc at a really wrong place Setting sysroot to The reason why it should be |
https://github.com/chromium/chromium/blob/master/docs/clang.md Seems like V8 uses a different clang binary than what we expect to compile stuff with. I need some help with this since I don't have much knowledge about these compiler stuff |
@thunder-coding The problem is |
The input errors seem to be prominent even after setting sysroot to |
|
This works, but at the cost of i18n support which is not desired. |
Can we just follow the official build guide for cross compiling v8? |
I tried this approach and build fails with some GN import errors. GN doesn't seem to respect |
V8 seems to have a lot of problems compiling for Termux. Should I skip adding it? Atleast we can have GN for those who would like to have it... |
Okay, so I have removed all my commits for V8. I might try if I can get it building in another PR. And about the |
TODOs:
Sample project compile well on aarch64 Android 11
termux_setup_gn
script- [ ] Add a package that requires gn to build to testtermux_setup_gn
- [ ] Add packagev8
- [ ]nodejs
link to sharedv8