-
Notifications
You must be signed in to change notification settings - Fork 4
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
build from current src/objdir? #1
Comments
Oh wow, I wasn't really expecting anyone to actually try using this. It's got a lot of usability issues, I'm redesigning it at the moment. (I'd appreciate any commentary on what you think is good or terrible about it, and what you'd like to see instead.)
To reuse your src tree, set the I haven't tried reusing an object directory, and doing so kinda goes against the intent of how this works, but I think you should be able to override |
hi Mark,
so basically my workflow is this:
i was hoping i could use bricoler to automate step 4, i.e. taking my existing src tree and booting it into a VM -- but, ideally, without having to rebuild everything from scratch, since i'm just testing a local change, not doing QA / RE. it might be bricoler isn't the right tool for this though, which is fine -- i don't mind writing some local scripts for it instead. i'll have a try with MAKEOBJDIRPREFIX. |
apologies if this is already documented but i didn't see it in README:
is there a way, using the vm-boot task, to re-use the existing src and obj directories for the build? the system i development on is quite low-end (Ryzen 5800X3D, 8x 3.4GHz cores) and buildworld takes a long time. i'm testing a commit that requires booting GENERIC on every architecture and it's taking a long time just to run buildworld/buildkernel for bricoler.
The text was updated successfully, but these errors were encountered: