a664c7088a
build: clean up git related scripts ( #663 )
2018-08-31 17:41:57 +02:00
392a5c0985
perf: commit our patches in batches instead of 1 by 1
2018-08-21 11:56:03 -07:00
5ff3486fc0
build: add optional --project-root arg for the patching related scripts ( #653 )
...
It is necessary because we have different folders hierarchy
in the traditional build setup with libchromiumcontent being a separate repo
and in the gn-based build with libchromiumcontent repo checked out inside the src/.
2018-08-16 14:11:33 -07:00
ea761327d7
Add an option to commit patches after they have been applied
2018-08-14 22:30:46 -07:00
bdfcdb0fe1
Only show download stats when verbose is used.
2018-07-13 13:40:31 -04:00
44c01668ad
Read 1mb instead of 1024 bytes
...
Also fix percentage sign
2018-07-13 11:34:54 -04:00
679db0e255
fix: syntax error introduced in 84560753
2018-07-11 09:03:59 -05:00
8456075339
chore: remove unsued variable in filesystem script
2018-07-11 10:39:31 +10:00
c842414712
build: improve percentage output in download script
2018-07-10 21:02:03 +10:00
4516433f23
build: improve the download script to show percentage / ratio progress of libcc download
2018-07-04 15:54:25 +10:00
5d684ac763
Bump up build timeout
...
Also, try to track down gn hanging.
2018-06-18 15:21:51 -04:00
44fb62a081
Use packaged chromium source for CI
...
Patch so that we can exclude native_client source
2018-05-09 12:30:06 -04:00
bde7bcb88c
Use sccache to speed up builds
...
New binaries with Azure support
Only use sccache for shared(debug) builds
2018-04-25 10:18:23 -04:00
b6e1832a2c
Add wrapper script for the bundled sccache
2018-04-19 13:41:56 +02:00
b3383e6c42
Add lib/sccache.py helper script
2018-04-16 15:52:13 +02:00
7711db5148
Add 'run-gn' script and call it from the 'update' script
...
Example usage:
$ ./script/run-gn -c shared_library tests
Done. Made 6931 targets from 1329 files in 3892ms
Done. Made 6918 targets from 1333 files in 3689ms
2018-04-12 13:22:14 +02:00
b420d585a0
Extract Ninja related stuff to lib/ninja.py
2018-04-12 13:22:14 +02:00
b0da43567f
Add and use git.get_head_commit()
2018-04-12 13:22:14 +02:00
3bb757b3fd
Move some script constants to a shared lib/config.py
2018-04-12 13:21:12 +02:00
788db449d4
Add script/get-patch
...
Use it to export commits from Chromium's and other repos as patch files.
2018-04-09 16:25:10 +02:00
dda2851946
Customized build clang scripts for arm64/armv7
...
In order to build/test Electron on arm7 and arm64 we need to manually build clang for those platforms. These scripts are modified versions of https://chromium.googlesource.com/chromium/src/tools/clang/+/master/scripts/update.py and https://chromium.googlesource.com/chromium/src/tools/clang/+/master/scripts/package.py
2018-03-21 13:31:21 -04:00
38c34c5446
Store patches meta info in patches configs ( #470 )
...
* Add PyYAML submodule
https://github.com/yaml/pyyaml
* Install PyYAML on bootstrap
* Ignore dirty state of the pyyaml submodule
It creates a "build" directory under its root when built.
* Use argparse in the apply-patches script
And provide a target arch as a named argument.
* Store patches meta info in patches configs
Use a patches config to defines order of patches,
specify a patch owner, and provide a description for a patch.
It should help us to avoid order collisions, make merge conflicts explicit,
and help find owners since git blame might not be reliable
because of frequent changes during Chromium upgrades.
2018-03-20 13:26:39 -05:00
0db9357d59
Use Visual Studio 2017
2018-03-15 14:50:03 +09:00
09d9bfabee
Merge pull request #468 from electron/refactor-patches-related-stuff
...
Light refactoring of patches related code
2018-03-06 10:14:44 +09:00
49a516a2e4
Light refactoring of patches related code
...
- create Patch, PatchesList, and PatchesConfig classes
- use Patch and PatchesList in patch.py script
- slightly improve apply-patches script
2018-03-05 13:27:56 +01:00
cb39877aff
Remove the code building for mips64el host
2018-02-27 14:44:22 +09:00
d0888fc619
Update gcc to 4.9 for mips64el target
2018-02-27 14:44:21 +09:00
21e022c89f
Run `gn` via depot_tools to ensure stable .ninja file output
...
The `toolchain.ninja` file contains commands that invoke Python. It is
important to ensure that GN always detects the same path to the Python
executable, otherwise when Ninja calls it to re-generate .ninja files, it
creates different toolchain command lines which results in rebuild of
everything. This side effect can cause double duration of the static_library
build.
2018-02-20 14:52:58 +01:00
7f6efc286c
Exctract GN related functions to their own file
2018-01-25 14:37:24 -08:00
f79ab01b69
Move scoped_cwd to lib/util
2018-01-24 22:57:27 -08:00
d6f5f1f750
Extract fs related helper functions into their own file
2018-01-24 22:57:02 -08:00
41f1f0286d
Add git helpers for scripts
2017-08-02 17:19:53 +03:00
a57ed72352
Use the "out-{arch}/{config}" format for build output directories
2017-03-14 21:49:02 +01:00
047855cf31
Set build env for VS
2016-05-08 10:35:06 +09:00
98a8ec5c6e
lib.util => lib.config
2016-05-08 10:16:35 +09:00
2cb322a1f2
Add build of ffmpeg without proprietary codecs
2016-02-18 22:14:42 +08:00
a67e45347f
Fix output dir for arm target
2015-06-15 17:28:04 +08:00
beb5ed794e
Remove some unused configs
2015-04-02 22:58:21 +08:00
Alexey Kuzmin
Samuel Attard
Aleksei Kuzmin
John Kleinschmidt
Charles Kerr
Samuel Attard
Alexey Kuzmin
Cheng Zhao
Ales Pergl