cross-compiling kinetic-c

[kinjalcpatel]

Is there any plan to provide cross-compilation support for kinetic-c?

While cross-compiling kinetic-c, i would like to compile all the dependencies separately. And provide path for libraries, just like you have done for OPENSSL_PATH.

[jphughes]

The project is looking for help. Any changes will be welcomed.

Jim

On Sep 9, 2015, at 11:31 AM, kcpatel83 notifications@github.com wrote:

Is there any plan to provide cross-compilation support for kinetic-c?

While cross-compiling kinetic-c, i would like to compile all the dependencies separately. And provide path for libraries, just like you have done for OPENSSL_PATH.

—
Reply to this email directly or view it on GitHub #32.

[kinjalcpatel]

Thanks for the quick response, Jim.

We are already working on it. We are spiting the vendor subdir builds outside of kinetic-c build. Building different repositories with a single makefile is a big issue for cross compiling. We can fix this for now. But how do we ensure that future development would not break the cross compilation. Especially if any more vendor dirs are added without testing the cross compilation, it will again break the cross compilation. The build setup of kinetic-c need to be redesigned thinking the cross compilation.
The vendor parts need to be built outside first, then kinetic-c build process will use the libraries and headers for the vendor parts to build. We will send a patch shortly.

Thanks,
Kinjal

[nitinkamble]

Thanks Kinjal for following this up. We really need the cross compilation support for kinetic-c.

Nitin