Skip to content

Conversation

@jandryuk
Copy link
Contributor

@jandryuk jandryuk commented Nov 8, 2021

bitbake expects deploy under tmp-glibc. When you delete tmp-glibc, it
complains when it finds deploy already populated. Put deploy back under
tmp-glibc.

Signed-off-by: Jason Andryuk jandryuk@gmail.com

This may not be backwards compatible, but there are clearly issues with deploy being a sibling to tmp-glibc. Users can always clear the two directories, update build-*/conf/auto.conf to remove DEPLOY_DIR, and rebuild.

bitbake expects deploy under tmp-glibc.  When you delete tmp-glibc, it
complains when it finds deploy already populated.  Put deploy back under
tmp-glibc.

Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
@dpsmith
Copy link
Member

dpsmith commented Feb 5, 2024

I am not sure I am on board with this approach. I never saw this issue and don't doubt it exists. I am just not certain this is the best way to deal with the issue. @crogers1, what do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants