-
Notifications
You must be signed in to change notification settings - Fork 357
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
cross-platform, cross-compile build toolchain #280
Changes from 1 commit
9686139
b57b921
d89202e
9c75430
45e487d
bf02e87
076ffe2
f3e69cc
6d2bbb8
1ff1de4
54fdc43
d0deb23
3954205
18c7b37
9cd7c6a
7f2e8cf
2f66df8
9e45f55
8297dab
63ac9d1
da5d322
de97277
80f16de
9359bb8
d339049
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -21,5 +21,9 @@ hs_err*.log | |
*.iws | ||
.idea | ||
|
||
# python binaries | ||
*.pyc | ||
|
||
# Build output. | ||
node | ||
cmake.out |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
import build_platform as b | ||
|
||
# b.execute_build(b.target_macos, b.arch_x86, b.build_all, node_enabled = True, cross_compile = True) | ||
b.execute_build(b.target_macos, b.arch_x64, b.build_all, node_enabled = True, cross_compile = True) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Isn't There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The way command-line switches and arguments are translated to changes in the produced binary build artifacts is (roughly) as follows:
Having said that, the above code of PS: in the next PR the code from |
||
|
||
# b.execute_build(b.target_linux, b.arch_x64, b.build_all, True, True) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why are most of the lines in this file commented out? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I used this file mostly for testing during the early build-system development, in the next PR this will be more fleshed out and become a feature to run an interactive CLI and choose from a set of pre-configured build-configurations |
||
|
||
# build Node.js only | ||
# def build_njs(target, arch): | ||
# b.execute_build(target, arch, [b.build_node_js], node_enabled = True, cross_compile = True) | ||
|
||
# build_njs(b.target_android, b.arch_arm) | ||
# build_njs(b.target_android, b.arch_x86) | ||
|
||
# build_njs(b.target_linux, b.arch_x86) | ||
# build_njs(b.target_linux, b.arch_x64) | ||
|
||
# # needs reboot here to turn Hyper-V off if Host-OS is Windows | ||
|
||
# build_njs(b.target_macos, b.arch_x86) | ||
# build_njs(b.target_macos, b.arch_x64) | ||
|
||
# # needs reboot here to switch to Windows-Containers | ||
|
||
# build_njs(b.target_win32, b.arch_x86) | ||
# build_njs(b.target_win32, b.arch_x64) |
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.
Why are curly braces commented out?
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.
I use those just by convention to make it easier for the eye to quickly read where the scope of a if-elif-else block starts and ends. This being said, for the next PR I have removed those where only a single line is inside the branch scope. From now on they are only used for if-elif-else blocks that contain multiple lines in their respective blocks (which was the original intent). Thanks for the feedback