Skip to content
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

Binary not found in Core Build Makefile project #328

Merged
merged 1 commit into from
Mar 19, 2023

Conversation

ewaterlander
Copy link
Contributor

Fixed the problem for Core Build Makefile projects that the output binary could not be found during launching when the user set the Build Output Location to "Build in project directory". The project was only looking for binaries in the "build" folder.

Fixed the problem for Core Build Makefile projects that the output
binary could not be found during launching when the user set the
Build Output Location to "Build in project directory".
The project was only looking for binaries in the "build" folder.
@github-actions
Copy link

github-actions bot commented Mar 17, 2023

Test Results

     592 files       592 suites   16m 45s ⏱️
10 065 tests 10 043 ✔️ 22 💤 0
10 187 runs  10 165 ✔️ 22 💤 0

Results for commit e12a04a.

♻️ This comment has been updated with latest results.

Copy link
Member

@jonahgraham jonahgraham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I think this is a workaround rather than the full solution as presumably the "correct" solution would be the output entry would update based on the setting "Build in project directory" or not. As launching seems to work as expected this is ready to go.

@jonahgraham
Copy link
Member

This is ready to go, but I don't understand why it consistently fails the same test so I have restarted it again. I think it is just a flaky test, but I want to make sure there is no unintended consequence here.

@jonahgraham jonahgraham merged commit a6a4bfc into eclipse-cdt:main Mar 19, 2023
@jonahgraham
Copy link
Member

Thanks @ewaterlander

@jonahgraham jonahgraham added this to the 11.2.0 milestone Mar 19, 2023
@jonahgraham jonahgraham added the build Build components of CDT, anything to do with running the compiler, using Make, CMake, or any builder label Mar 19, 2023
@ewaterlander
Copy link
Contributor Author

LGTM. I think this is a workaround rather than the full solution as presumably the "correct" solution would be the output entry would update based on the setting "Build in project directory" or not. As launching seems to work as expected this is ready to go.

Currently a Core Build Makefile project will just launch the first binary found in the binaries container. The real output location also depends on the launch mode set in the LaunchBar. If you set the location to "configuration specific directory" and switch from Run to Debug without cleaning you will not see debug info, because the first binary under "build" is found in the build subdirectory "default".

The project doesn't control the content of the Makefile. In theory the binary could be written anywhere, even with location set to "configuration specific directory". The user needs to be aware which binary is built. It is currently not foolproof.

@ewaterlander
Copy link
Contributor Author

Thanks @ewaterlander

Thanks for merging.

@ewaterlander ewaterlander deleted the no_binaries branch March 23, 2023 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Build components of CDT, anything to do with running the compiler, using Make, CMake, or any builder
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants