We could resort to a middle ground. Instead of having an amalgamation
script that generates a single file, simply have a file that includes
everything and compiles that one. Which should also work.

The javascript port can likely be superseded with some form of support in
nnvm compiler, which transpires and generate likely more efficient code
than current version.  We can enable that feature now except that there is
no dedicated developer on it yet. We can talk about full deprecation after
this


Tianqi

On Mon, Nov 20, 2017 at 2:47 PM, Pedro Larroy <pedro.larroy.li...@gmail.com>
wrote:

> Hi all
>
> Given that we have working builds for ARM, Android, TX2 and the main
> architectures, and after considering how amalgamation is done. I would
> like to propose that we deprecate and remove amalgamation.
>
> I don't think the cost of maintaining this feature and how it's done
> justifies the ROI, given that we can now produce binary builds for
> embedded platforms in a comfortable way. It's also consuming build &
> test resources.
>
> We should strive to simplify our build system and development process.
>
> Pedro.
>

Reply via email to