| [cdt-dev] Gerrit review for core build autotools |
|
Hi, I’d like to submit patches on core build autotools project for review, although I’d like to get some advice before getting started. Are there any concerns to enable a basic core build autotools implementation first and gradually beef up the features over time? For the time being I plan to focus on enabling cross toolchains,
although I had some quick look at org.eclipse.cdt.autotools.core & org.eclipse.cdt.autotools.ui plugin.xml and realized that it will take some time for core build implementation to be as feature complete as the MBS counterpart. Is it OK for core build implementation
to coexist (i.e. enable in the builds) with the MBS implementation? Is there a minimum expectation of features that need to be implemented or supported for a new C/C++ project type? So far I’ve managed to get the basic stuffs working by looking at the CMake project,
e.g. new template wizard, a simple template manifest, nature, build config provider, build config. I’m able to build and debug simple autotools project natively but that’s pretty much it for now. Is it alright for me to submit patches for gerrit review to
get some feedback? Are there any preference on the naming or source tree location of the new plugins? I’ve tentatively created new plugins as build/org.eclipse.cdt.corebuild.autotools.core, build/org.eclipse.cdt.corebuild.autotools.ui
and build/org.eclipse.cdt.corebuild.autotools-feature, please let me know if this is alright and I’ll update them as required. --Chin Huat |