Here is discussion:

https://github.com/apache/incubator-mxnet/issues/8702

On Tue, Mar 6, 2018 at 9:14 AM, Chris Olivier <cjolivie...@gmail.com> wrote:

> This was agreed upon some time ago in a github issue thread, unless there
> are new objections to it.
>
> As far as I know, it's just a matter of someone putting in the work to add
> more functionality to cmake or to fuse the two builds.
>
> One solution for the short term might include having the Makefile launch
> cmake for most of the build and fall back to Makefile for some of the
> remaining stuff, like scalapkg, rpkg, etc.
>
> btw, cmake uses the openmp in 3rdparty
>
>
>
> On Tue, Mar 6, 2018 at 8:51 AM, Pedro Larroy <pedro.larroy.li...@gmail.com
> > wrote:
>
>> Hi
>>
>> I would like to raise the issue that maintaining two overlapping build
>> systems is too much overhead. It adds unnecessary complexity and
>> differences on how the project is built.
>>
>> For example, openmp is used differently from CMake and Make, in the former
>> the one provided by gcc is used and in the later is compiled from the
>> 3rdparty folder.
>>
>> I think this situation is not sustainable for the project, and specially
>> if
>> we add that we want to support compilation and cross compilation on
>> devices.
>>
>> My proposal would be to identify any gaps that are not covered by the
>> CMake
>> build system, cover them and make CMake the single build system for MXNet,
>> well tested and fully supported.
>>
>> Pedro.
>>
>
>

Reply via email to