[graalvm-dev] Avoiding NINJA dependency

[Gilles Duboscq]

Hi Foivos,

We actually moved from Makefiles to ninja to help support non-unix platforms.
The ninja files are generated though so i guess you could implement an alternative generator that creates Makefiles.
You can have a look at `mx_native.py` [1] for the generation of the ninja files. `NinjaBuildTask` has `needsBuild` / `build` / `clean`.
Something similar could be done with make, then we can add some flag that uses a different class for native projects (e.g., `DefaultMakeNativeProject` instead of `DefaultNativeProject`).

 Gilles

[1]: https://github.com/graalvm/mx/blob/master/mx_native.py

On 28/04/2020 15:31, Foivos Zakkak wrote:
> Hello all,
> 
> I am trying to avoid the dependency on NINJA when building native libraries like libchelper.
> Are you aware of any way to achieve this without manually writing Makefiles?
> 
> Additionally, if I were to write the required Makefiles and alter the corresponding suite.py files is there any chance such a change would make it upstream or is NINJA the only way forward?
> I see that makefiles are only used by sulong at the moment.
> 
> Thanks
> -- 
> 
> Foivos Zakkak
> 
> Senior Software Engineer, R&D Product Middleware
> 
> Red Hat <https://urldefense.com/v3/__https://www.redhat.com__;!!GqivPVa7Brio!IxC-AQYSTh7M2kDyVowp6AdQFBTypGVR3YBR31dp586yDD2u6XGy0_Nxre--NZSYbjpwaA$>
> 
> 7B4069D929BAAE91C0B3220A0846BFD103F04EA1
> 
> 
> _______________________________________________
> GraalVM-Dev mailing list
> GraalVM-Dev at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/graalvm-dev
>