Re: [cdt-dev] Getting started with CDT development

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi Tony,

1. Please change the order of Getting started with CDT development*. 

2. Your changes are good - strangely I didn't get notified of the changes :-( 

3. I had a look - create the "src" directory (e.g. mkdir src) and the error goes away. If you (or someone else) knows the correct incantation of build.properties so that the src directory isn't needed, or perhaps a dummy file so that git preserves the empty directory? Changing just the .classpath isn't correct as the next time someone does Plug-in Tools -> Update Classpath the problem will be restored.

Other items you raised:

- CDT Devel.launch - I raised Bug 567738 so that future people don't trip up on that - your conclusion was correct, it is a special purpose launch with a generic name.

- The " error occurred due to missing required components" is a problem, I suppose the workaround is good enough, but my lack of Oomph experience in this regard means I don't know. If you have more of an error please raise a bug and CC Alexander F.

* long version:

Jantje is correct, many of the active committers have never got on board with Oomph preferring manual setup and configuration. However Alexander F has been doing a good job of keeping CDT.setup working well since he took on the task earlier this year. Please do leave the note about reaching out to cdt-dev (perhaps removing the word experimental). The upside of manual configuration is that it is a little more like what happens with the build (i.e. using cdt.target) and the downside of the Oomph setup is there is currently no way to automate test that the Oomph setup works.

Thanks

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Thu, 8 Oct 2020 at 17:07, Homer, Tony <tony.homer@xxxxxxxxx> wrote:

It seems that “CDT Devel” (https://git.eclipse.org/r/plugins/gitiles/cdt/org.eclipse.cdt/+/refs/heads/cdt_10_0/cmake/aggregator/CDT%20devel.launch)  is not intended to be used for getting started with CDT Development.

 

I created a new launch configuration with defaults and it works.

Sorry for the giant log file in the previous message.

I removed it from this response.

 

I’d still like feedback on the points I raised in the original message in this thread.  In short,

1. Oomph is a more efficient quick-start, so I’d like to rearrange the “Getting started” page to put that at the top
2. I ran into some errors and edited the “Getting started” page – let me know if the edits are sane.
3. 'org.eclipse.cdt.meson.ui.editor' is missing required source folder: 'src/'.  Is it expected?

Please see below for the original details.

 

Thanks!

Tony

 

From: "Homer, Tony" <tony.homer@xxxxxxxxx>
Date: Thursday, October 8, 2020 at 1:50 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: Getting started with CDT development

 

I ran through the Oomph steps again, picking Product Version “Latest (2020-12)” and Target Platform 2020-12.

An error occurred due to missing required components, but after clicking Back and then Finish, Oomph continued and completed successfully.

I still have the error with “Project 'org.eclipse.cdt.meson.ui.editor' is missing required source folder: 'src/'”, which I worked around by removing this src from Java Build Path.

 

When I tried to launch the “CDT Devel” debug configuration, it failed to launch with the error log below.

I will continue on my own, but decided to share this with the list in case there is a simple solution that someone knows of.

 

<removed giant log file>

 

From: "Homer, Tony" <tony.homer@xxxxxxxxx>
Date: Thursday, October 8, 2020 at 1:26 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: Getting started with CDT development

 

I spoke too soon about Oomph.

It appeared to build, but when I tried to launch the “CDT Devel” debug configuration, a bunch of errors appeared.

I’ll continue troubleshooting the setup and provide an update when I get a working workbench that can successfully launch the “CDT Devel” debug configuration.

 

From: "Homer, Tony" <tony.homer@xxxxxxxxx>
Date: Thursday, October 8, 2020 at 1:18 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Getting started with CDT development

 

I am setting up my workspace according to https://wiki.eclipse.org/Getting_started_with_CDT_development.

I made some minor updates to the page as I worked through it.

I decided to try both paths.

1. Set everything up manually
2. Using Oomph

 

Using Oomph is definitely faster, so I’d like to rearrange the page to put that at the top.

I have a mostly working workspace with Oomph, whereas my manual approach is still on 10s of thousands of errors, refreshing target platform, setting API baselines, etc.

I’m sure I’ll get there eventually with the manual approach, but the Oomph approach is much more efficient.

 

The Using Oomph section says to ask questions here if errors occur.

I have a few comments.

 

First, I did run into errors while setting up with Oomph, but was mostly able to resolve them simply by clicking back and next.  I imagine this was due to some requests timing out and eventually everything resolved.  I added a note to the wiki suggesting to do this as a troubleshooting step.  It seems fine to me, but I wanted to call it out in case anyone cares to comment.  I’d be happy to go through the install a few times in order to capture more detailed information.

 

Second, I have a very simple but strange error which I can work around, but I wanted to call it out.
Project 'org.eclipse.cdt.meson.ui.editor' is missing required source folder: 'src/'

I can simply remove the src folder from the build, but this modifies the classpath vs. what is checked in, which makes me doubt this approach.

Is there something I should do other than remove the src folder from the build path?

 

Thanks!

Tony Homer

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cdt-dev