Hello folks.
When devising repeatable patch building from a different repo i found that being able to do the above is helpful and allows for intermediates like the generated code to go to build directories for cleanup etc.
Interesting?
My fork contains a branch dev that implements something that works for me.
It adds --out_dir to allow output relocation.
It performs os.chdir() to assure that program-relative paths resolve.
One side effect of these changes is enhancing the rewrite of the target Makefile to point to libdaisy no matter where the generated output goes.
There are still places where one needs to pass absolute paths to the program (--out_dir being one), but these could be fixed up to allow relative paths to work too.
Hello folks. When devising repeatable patch building from a different repo i found that being able to do the above is helpful and allows for intermediates like the generated code to go to build directories for cleanup etc. Interesting? My fork contains a branch
devthat implements something that works for me. It adds--out_dirto allow output relocation. It performsos.chdir()to assure that program-relative paths resolve. One side effect of these changes is enhancing the rewrite of the target Makefile to point to libdaisy no matter where the generated output goes. There are still places where one needs to pass absolute paths to the program (--out_dirbeing one), but these could be fixed up to allow relative paths to work too.