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
grc: A generated python hier_block is written to the wrong directory #5547
Conversation
The generated code is written to the directory of the generating grc file instead to the 'hier_block_lib_dir' directory. cpp generated code ends up in the correct directory. This error was introduced with commit af3fbe4 FIxes gnuradio#5531 Signed-off-by: Volker Schroer <3470424+dl1ksv@users.noreply.github.com>
|
Does this still work with grcc? #4871 makes it seem like this change was intended. Should the correct directory be passed in from above instead of ignored? |
Signed-off-by: Volker Schroer <3470424+dl1ksv@users.noreply.github.com>
|
Good point. Without my patch After my patch in both cases the code is written ~/.grc_gnuradio. All other combinations of generation option and output language are not affected by my patch. |
Shouldn't the output given |
|
Yes, but I wanted to point out, that this was not the case without any patch. After my first commit the code for the hier block is written to ~/.grc_gnuradio , independently of the the output language. For other types the code is written to the correct directory. |
|
Ah ok - I didn't get the distinction between the two commits. Thanks! |
|
Tested and working - sorry for the delay and thank you for the fix. |
Pull Request Details
The generated code is written to the directory of the generating grc file
instead to the 'hier_block_lib_dir' directory.
cpp generated code ends up in the correct directory.
This error was introduced with commit af3fbe4
Description
Take the directory from the config settings ( as before)
Related Issue
Fixes #5531
Testing Done
Tested with different hier blocks
Checklist