I have looked over the spec
(https://github.com/gradle/gradle/blob/master/design-docs/dependency-model.md).
Some of the questions I have are time / schedule related and some are just to
see if the upcoming native support fits our needs.
Right now, we have make files for all of our native builds. Some of these I
could get rid of and just use Gradle to build. However the GStreamer & WebKit
make files are likely out of scope to convert -- we want to build the way
WebKit & GStreamer normally build, not rewrite their entire build system. So I
expect to end up doing something custom for those two cases.
In all other cases, we have to do the following:
- Use different compilers on different platforms
- Developers might develop using a free compiler on Windows
for example, but then we use a commercial compiler for
creating
the actual releases.
- gcc on Mac / Linux, but the Visual Studio compiler on Windows
for example
- Compile C / C++ / Objective-C
- Different compiler options depending on platform and project.
- For example we pass the -DNDEBUG param when building the font
natives,
-Wl when compiling on Linux and not Solaris, etc.
- Cross compile builds
- A single build can produce x86, ARM hard float, ARM soft float
- Build some native code on some platforms but not on others
- D3D can only be built on Windows, OpenGL we build on
everything
I looked briefly at the existing C++ plugin but it didn't look like it
supported different compilers.
Is the new native support going to provide for all these use cases? Compiling
of Objective-C as well?
What is the schedule for the new native support?
Thanks
Richard
