Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] What exactly is CDT core build?

Hi Martin, sorry for the late reply; didn't notice this was directed to me.

Core build is relatively young and was an initiative started by Doug to simplify the build mechanism especially in the case where
the build mechanism took care of most things internally (e.g. Makefile, CMake, meson).  It was essentially still a work in progress when Doug left and he started simple
with the intention that others would modify it as needed.  My experience with it was to add meson support and allow Docker Containers to be used as targets.

Regarding Core build and .cproject, there are no set rules.  It was my understanding that Core build attempted to simplify the myriad of settings and probably why the initial
version hard-coded using the config name.  If the wizard doesn't need to store a setting, then that can be modified.

-- Jeff J.

On Wed, Aug 19, 2020 at 1:42 PM 15 knots <fifteenknots505@xxxxxxxxx> wrote:

Am Mi., 5. Aug. 2020 um 01:33 Uhr schrieb Jonah Graham <jonah@xxxxxxxxxxxxxxxx>:
> Hi Martin,
> Core build was written by Doug - he isn't active here anymore.
> Jeff has the most experience with Core build AFAIK.
> @Jeff, can you comment on any of Martin's questions, or direct us to the best place to find the answers?
> Thanks,
> Jonah
> ~~~
> Jonah Graham
> Kichwa Coders
> On Tue, 4 Aug 2020 at 16:28, 15 knots <fifteenknots505@xxxxxxxxx> wrote:
>> Hi all,
>> What exactly is core build compared to managed build? Are there any
>> concept papers that explain it? I found standard build [1] in the CDT
>> wiki.
>> Which packages belong to the scope of core build?
>> I am evaluating a path to improve cmake build support for CDT that
>> takes the CMakeLists.txt as the source of truth. I already did that
>> for managed build (cmake4eclipse), but MBS gives a project
>> configuration UI that is confusing to users: Lots of the input fields
>> simply have no effect if the project uses cmake to generate build
>> scripts.
>> Looking at the CDT code base, I found at least one discrepancy:
>> The CMake-project-creation wizard put a <pathentry> for the output
>> location into the .cproject file, but CBuildConfiguration.class
>> hard-codes the location to be
>> project.getFolder("build").getFolder(configName).
>> Is core build supposed to use .cproject to store the preferences any longer?
>> Regards, Martin
>> [1]
>> _______________________________________________
>> cdt-dev mailing list
>> cdt-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit
cdt-dev mailing list
To unsubscribe from this list, visit

Back to the top