-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting Started documentation update. #1056
Conversation
Hi @jonahgraham @jld01 @betamaxbandit , Would you like to review this change? It is not finished yet. I'm going to add topics about Building, Running, and Debugging. You can start adding comments. I separated CBS and MBS. |
Test Results 600 files - 34 600 suites - 34 13m 17s ⏱️ - 22m 50s Results for commit dfcb2fa. ± Comparison against base commit 0fcf41a. This pull request removes 1217 tests.
♻️ This comment has been updated with latest results. |
I'll have a look soon - in the meantime since I don't have an auto comment, the docs are available from this build in https://github.com/eclipse-cdt/cdt/actions/runs/12933695063?pr=1056 (docs link near the bottom) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks very good, I think how you have split it up is very useful.
|
||
== Launch Bar | ||
|
||
CBS projects rely on the *LaunchBar*. Make sure the launch bar plugin |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CBS projects rely on the *LaunchBar*. Make sure the launch bar plugin | |
Core Build System (CBS) projects rely on the *Launch Bar*. Make sure the _LaunchBar UI_ feature |
This tutorial describes how to use existing code for Core Build System | ||
projects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tutorial describes how to use existing code for Core Build System | |
projects. | |
This tutorial describes how to create a new Core Build System | |
project for use with existing code. |
=== Using an existing CMake project | ||
|
||
To create an empty CMake project select the template *Empty or Existing CMake | ||
Project* in the *New C/{cpp} Project* wizard. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to clarify the distinction between a "CMake project" (IDE independent source code) and a "CMake project" (metadata created by CDT).
|
||
image:cbs_empty_cmake_project.png[Empty or Existing CMake Project] | ||
|
||
Then in the *New CMake Project* wizard deselect *Use default location* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then in the *New CMake Project* wizard deselect *Use default location* | |
In the *New CMake Project* wizard deselect *Use default location* |
=== Using an existing Makefile project | ||
|
||
Create a Makefile project as described in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similarly, distinguish the two uses of "Makefile project" here.
In the *New Makefile Project* wizard deselect *Use default location* | ||
and set the location of the existing code, and deselect *Create Hello |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the *New Makefile Project* wizard deselect *Use default location* | |
and set the location of the existing code, and deselect *Create Hello | |
In the *New Makefile Project* wizard deselect *Use default location*, | |
set the location of the existing code, and deselect *Create Hello |
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think multiple empty lines (here and elsewhere) are being interpreted as the end of the numbered list. So the next numbered list item will be item "1" again. Try a single empty line only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had some problems with keeping numbered lists together too, I ended up having to add +
at the beginning of the blank lines to show list continuation. See https://docs.asciidoctor.org/asciidoc/latest/lists/continuation/#list-continuation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments on your work-in-progress, @ewaterlander. Great to see the documentation being updated.
c429387
to
9526216
Compare
I added three new topics: Building, Running, and Debugging a project. Now the change is complete. I will process the comments on Monday. Thanks. Have a nice weekend! |
9526216
to
378d553
Compare
Hi, |
Hi @jld01 and @jonahgraham , Could you have a look again? I think the work is done now. kind regards, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ewaterlander ,
thanks for updating the docs.
I've made a few suggestions.
Cheers John
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Build Settings tab has recently changed a lot
See #1046 (comment)
== Using existing code | ||
|
||
This tutorial describes how to create a new Core Build System | ||
(CBS) project for use with existing code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It assumes existing code is located in a directory containing source files. Note, CDT project files are written into this directory.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
Using existing code is done by creating a new **empty** project on top of the | ||
existing code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[I think this task is quite unintuitive for the new user, so it's worth labouring the point about project files, directories etc]
Using existing code is performed by creating a new empty CDT project in the top directory containing the existing source files. With this method, new project files are created, but no new project directory is created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
|
||
image:cbs_empty_cmake_project.png[Empty or Existing CMake Project] | ||
|
||
In the *New CMake Project* wizard deselect *Use default location* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[Consider replacing "deselect" with "uncheck". Feels a little more user friendly. There are a couple more occurrences of this below]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think @betamaxbandit's comments are worth addressing now, or in a follow-up. I have a TODO in the CDT 12 N&N to update the screenshot:
cdt/NewAndNoteworthy/CDT-12.0.md
Line 23 in 84d99f2
TODO: Before release add the final screenshot for the build settings here. I am not including it now because the UI keeps changing. |
But there is some flexibility on that file being updated because it can happen after our last build. The screenshots in the online help need to be updated before final build to populate https://help.eclipse.org/latest/index.jsp and built-in help
I have created #1064 and added updating doc/org.eclipse.cdt.doc.user/images/cbs_build_settings_tab_cmake.png to the check-list.
Hi, |
Thanks for the updates, @ewaterlander. |
* Put Core Build and Managed Build items in separate topics. * Added two images to Creating a CMake project. * Added new pages about creating a CBS Makefile project, using existing code, launch bar, building, running, and debbuggin a project. * Renamed "Creating a simple application" to "Creating a Managed Build System Makefile project" and replaced two images. * Removed "Creating a Makefile project", because it was duplicate information. Fixes eclipse-cdt#992
6ba2488
to
dfcb2fa
Compare
Hi @jonahgraham and @betamaxbandit , I updated the image and addressed the comments. |
I squashed and rebased the commit. After rebasing I lost some time, because Eclipse-Committers did not properly refresh the work area, which cause build errors in my environment. :( |
That is frustrating - I think the other day I had a fail to refresh properly error, I couldn't reproduce it and I am not sure what happened. |
Thanks @ewaterlander |
Fixes #992