-
Notifications
You must be signed in to change notification settings - Fork 0
Pr/common/build #6
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
Conversation
thanks for helping, I get this error
also I'm not sure about adding the test because its scope and purpose is very different, i.e. checking the build/make system and not RIOT code. So maybe such should rather go into |
Mac https://github.com/smlng/RIOT/pull/6/files#diff-ebbb3165b3276a049759e5cb4e04d6a4R715 A solution could be to replace it with The test was not 100% necessary, it was just to show that the new directory was lacking a proper docker integration. And if a mistake can be made like this, having a test verifying it still works is for me important. There is already build system/BSP tests like The build system is part of the riot distribution, if not, we coul remove it and the |
b70c936
to
d625b57
Compare
Hmm just noticed than it is complaining about Does this work ? (would explain things about MAKEOVERRIDES)
or this ? (with the directory with a slash but still on the command line)
|
@cladmi when I manually create the directory, i.e. |
Yep that is the reason. If I comment the target with the
So It looks like it is an issue with I will update my branch to test the fix he did. |
If this works, I can do a single PR to discuss the directory creation rule. To not wait for it, the other solution is to do the |
The 'build' directory should not be tracked by git.
82bd1af
to
47d5831
Compare
does work now on macOS (after rebasing on latest RIOT master). How to proceed here? You wanna squash yourself or should I merge and squash you commits in my branch? |
I will do a PR on RIOT about directory creation. Because the way I did it for the moment is also wrong. A target should never directly depend on a directory as the directory modification date is the last created file inside. It should be done by using an order only dependency. But as I tested before and re-verified, this does not work when doing For the time being I will replace with only doing a |
The directory variable should not be exported as it is an 'host' path. It should however be mounted in the container.
The 'build' directory should be created before starting docker. If not it will be created as root. Also add mapping for the directory in docker. Currently create the directory in the target until there is a directory creation target.
47d5831
to
ce39ee8
Compare
I replaced with creating the directory in the target. I also currently removed the test. I re-ran the test from the previous branch and it is working. You can merge/rebase in your branch if you want. |
Contribution description
This should address my remarks from comment
RIOT-OS#10038 (review)
Testing procedure
It should work without errors.
To make it more visible, the
$(Q)
can be removed in the file creation target.I put the commit in an order with the test first, so it can be tested without the fix more easily by doing
git checkout
on the test commit. They will need to be re-organized later.Issues/PRs references
RIOT-OS#10038