-
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
The active Launch Target is now saved in the ICBuildConfiguration #1076
base: main
Are you sure you want to change the base?
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
22f1648
to
382ce1e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
382ce1e
to
a98d721
Compare
This comment was marked as resolved.
This comment was marked as resolved.
a98d721
to
4871559
Compare
This comment was marked as outdated.
This comment was marked as outdated.
cmake/org.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfiguration.java
Outdated
Show resolved
Hide resolved
cmake/org.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfiguration.java
Outdated
Show resolved
Hide resolved
cmake/org.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfiguration.java
Outdated
Show resolved
Hide resolved
...g.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfigurationProvider.java
Outdated
Show resolved
Hide resolved
...g.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfigurationProvider.java
Outdated
Show resolved
Hide resolved
...g.eclipse.cdt.cmake.core/src/org/eclipse/cdt/cmake/core/CMakeBuildConfigurationProvider.java
Outdated
Show resolved
Hide resolved
core/org.eclipse.cdt.core/src/org/eclipse/cdt/core/build/CBuildConfiguration.java
Outdated
Show resolved
Hide resolved
...org.eclipse.cdt.core/src/org/eclipse/cdt/internal/core/build/CBuildConfigurationManager.java
Show resolved
Hide resolved
....eclipse.cdt.debug.core/src/org/eclipse/cdt/debug/core/launch/CoreBuildLaunchBarTracker.java
Show resolved
Hide resolved
4871559
to
23f9e03
Compare
In addition to the active launch mode and toolchain, the active Launch Target is now used to determine the Core Build Configuration (ICBuildConfiguration). The build output folder name now ends with the name of the Launch Target (eg: cmake.debug.win32.x86_64.Local) Additionally, API added to allow the ISV to configure the build output folder name. The ICBuildConfigurationProvider implementations, shown below, have been tidied up to use common code. CMakeBuildConfigurationProvider AutotoolsBuildConfigurationProvider MakefileBuildConfigurationProvider MesonBuildConfigurationProvider Addresses Issue: CDT CMake Improvements eclipse-cdt#1000, IDE-82683-REQ-016 Launch Targets used in ICBuildConfiguration Addresses Issue: CDT CMake Improvements eclipse-cdt#1000, IDE-82683-REQ-018 Build output folder name
23f9e03
to
c718fb0
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
I see the "Code Cleanliness Checks / build (pull_request) Failing after 3m" job failed for my PR, but in the detail I don't see what the problem is. Can you help please? |
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.
@betamaxbandit There are a few small changes which I will apply manually. Please have a look and let me know if they are ok. And if so I will merge them
I did test autotools and it looks fine.
...eclipse.cdt.core.tests/model/org/eclipse/cdt/core/build/CBuildConfigurationManagerTests.java
Outdated
Show resolved
Hide resolved
...eclipse.cdt.core.tests/model/org/eclipse/cdt/core/build/CBuildConfigurationManagerTests.java
Outdated
Show resolved
Hide resolved
/* | ||
* Note, this extra test uses getName on CBuildConfiguration rather than the API ICBuildConfiguration | ||
*/ | ||
String name = cbc.getName(); |
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.
Is this the place you were mentioning that you wanted me to check about use of non-API?
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, that's it
...lipse.cdt.core.tests/model/org/eclipse/cdt/core/build/ICBuildConfigurationProviderTests.java
Outdated
Show resolved
Hide resolved
core/org.eclipse.cdt.core/src/org/eclipse/cdt/core/build/ICBuildConfigurationManager.java
Outdated
Show resolved
Hide resolved
@betamaxbandit here is a link to to my application of the changes in the review tab. It can also be seen by clicking on the commit in the timeline above: |
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.
LGTM.
Hi @jonahgraham ,
thank you for all your suggestions. I agree with all of them.
I see "Apply review comments", but can't click it.
Please go ahead and commit these if that is what you meant.
Thanks John
Great, thank you. I'm happy with all the changes you suggest. |
@betamaxbandit I think this is ready to squash and merge. Let me know when you are done your final check. |
Hi @jonahgraham , |
In addition to the active launch mode and toolchain, the active Launch Target is now used to determine the Core Build Configuration (ICBuildConfiguration).
The build output folder name now ends with the name of the Launch Target (eg: cmake.debug.win32.x86_64.Local)
Addresses Issue: CDT CMake Improvements #1000, IDE-82683-REQ-016 Launch Targets used in ICBuildConfiguration