OK.. I'm just expressing my own opinion, and I just want to keep things consistent with WebGL / OpenGL. It's not quite a big issue for me where the headers are hosted.
You mentioned that you want to avoid adding new commits (especially ones which have no chance of being upstreamed) to chromium-crosswalk, this raises another concern for me. For historical reasons, by now almost all WebCL code are located in src/WebKit/Source/modules/webcl, and this minimizes the effort required during rebase. However, strictly speaking this is not the right architecture because system hardware is accessed within Blink. We are considering moving some code from Blink to src/content and migrating to Chromium's multi-process model gradually so that WebCL can be used on platforms other than Android. This will apparently be a much more complex task than committing the OpenCL headers (see how WebGL is implemented), so I'm afraid that will be totally contrary to the philosophy of avoiding new commits. BR Jiajie -----Original Message----- From: Crosswalk-dev [mailto:[email protected]] On Behalf Of Raphael Kubo da Costa Sent: Friday, August 28, 2015 5:05 PM To: [email protected] Subject: Re: [Crosswalk-dev] Intent to switch: using our own GitHub copy of the OpenCL headers "Hu, Jiajie" <[email protected]> writes: > Thanks for proposal and actually I have had the same idea for a long > time that SVN should no longer be used for the OpenCL headers. > > However, I prefer to add these headers to third_party/khronos in > chromium-crosswalk.git like > https://github.com/crosswalk-project/chromium-crosswalk/pull/188, just > as how OpenGL headers are managed in Chromium, instead of hosting them > in a dedicated repo. > > WDYT? Is there a reason why you think this is a better approach? I'd like to avoid adding new commits (especially ones like this which have no chance of being upstreamed as-is) to chromium-crosswalk if at all possible, so putting things in a separate repository was the best I could come up with. _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
