| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-land of crrev.com/1082083005
The previous remoting webapp GN build files were not enabled and at
least 6 months out of date. This cl fixes the problem by bringing
the build rules up to date and enables the webapp build.
It also starts to move all the remoting-specific build rules into
the remoting dir rather than having them in the main build.gn file.
BUG=
Review URL: https://codereview.chromium.org/1096783002
Cr-Commit-Position: refs/heads/master@{#325733}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
#5 id:80001 of https://codereview.chromium.org/1082083005/)
Reason for revert:
Suspected of breaking the build. For details, see https://code.google.com/p/chromium/issues/detail?id=477869
Original issue's description:
> [Chromoting] Enable remoting webapp main.html GN build.
>
> The previous remoting webapp GN build files were not enabled and at
> least 6 months out of date. This cl fixes the problem by bringing
> the build rules up to date and enables the webapp build.
>
> It also starts to move all the remoting-specific build rules into
> the remoting dir rather than having them in the main build.gn file.
>
> BUG=
>
> Committed: https://crrev.com/62ee8a9cfebbc8bdc037aaa3b37ebfbb45e02472
> Cr-Commit-Position: refs/heads/master@{#325551}
TBR=dpranke@chromium.org,garykac@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
Review URL: https://codereview.chromium.org/1090023004
Cr-Commit-Position: refs/heads/master@{#325556}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previous remoting webapp GN build files were not enabled and at
least 6 months out of date. This cl fixes the problem by bringing
the build rules up to date and enables the webapp build.
It also starts to move all the remoting-specific build rules into
the remoting dir rather than having them in the main build.gn file.
BUG=
Review URL: https://codereview.chromium.org/1082083005
Cr-Commit-Position: refs/heads/master@{#325551}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-land of crrev.com/896743004/, which was reverted in crrev.com/905223002/
Previous build problem was due to some linux variables being defined by a script which in turn had some dependencies on dpkg-architecture (which is not present for all linux builds).
Fix is to move the var definitions in with the targets.
BUG=
Review URL: https://codereview.chromium.org/906463005
Cr-Commit-Position: refs/heads/master@{#315670}
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(patchset #8 id:140001 of https://codereview.chromium.org/896743004/)
Reason for revert:
It cause ChromiumOS.Chromium and PFQ bots to fail. The reason might because chroot didn't have "dpkg-architecture" command. The correct solution might be add "dpkg-architecture" command to chroot. But this CL currently break PFQ and a bunch of bots. So revert it for immediate fix.
See crbug.com/456491
Original issue's description:
> [Chromoting] Remove wildcard ('*') from remoting_all target.
>
> Support for the wildcard is going away in GN, so this helps prepare for the transition away from GYP.
>
> This cl adds dummy targets so that that logic for when the proper targets should be build can be kept in the platform-specific files.
>
> Some of the conditions in the host gyp files needed to be restructured so that the dummy targets would be defined only when necessary. The updated conditions caused a lot of lines to be re-indented, but the target definitions are the same (except for the new dummy targets).
>
> BUG=
>
> Committed: https://crrev.com/9fb75ed89c0ae4ced679576f9cf030cc8c30e928
> Cr-Commit-Position: refs/heads/master@{#315150}
TBR=kelvinp@chromium.org,garykac@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
Review URL: https://codereview.chromium.org/905223002
Cr-Commit-Position: refs/heads/master@{#315261}
|
|
|
Support for the wildcard is going away in GN, so this helps prepare for the transition away from GYP.
This cl adds dummy targets so that that logic for when the proper targets should be build can be kept in the platform-specific files.
Some of the conditions in the host gyp files needed to be restructured so that the dummy targets would be defined only when necessary. The updated conditions caused a lot of lines to be re-indented, but the target definitions are the same (except for the new dummy targets).
BUG=
Review URL: https://codereview.chromium.org/896743004
Cr-Commit-Position: refs/heads/master@{#315150}
|
