-
Notifications
You must be signed in to change notification settings - Fork 11
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
REDHAWK IDL PROJECT into Target SDR #14
Comments
You can install these interfaces by creating custom IDL projects in the IDE and adding your IDL files to these projects. These projects include the automake hooks to install the stubs in the appropriate place and for you to be able to create ports that implement the interfaces |
Hello @maxrobert, thanks for your reply. Is there anyway to create a vocoder and an encryptor component using these IDL files. I know using cpp we can create REDHAWK components. But is there any other alternative for creating components in advance. Thanks in advance. |
I'm not sure I understand the question. The model that REDHAWK follows for leveraging custom IDL is with a "has a" rather than an "is a" pattern. If you were to create a REDHAWK component with these IDL as the port definition for one of its "provides" ports, it'd generate the server-side stubs in the project's port_impl.* files. The port object is instantiated as part of the component's deployment cycle. The component implements the base interfaces for lifecycle/housekeeping and the port would be for your use in your case-specific functionality |
@maxrobert Thanks for your reply. I have an another problem please help me if you could. I am trying to install few components into my TARGET SDR from the git repo: https://github.com/lmcadoo2/RedhawkComponents. checking for fec_v3... no What should I do to overcome this? Kindly help. Thank you. |
@jsrsarma @ryanbauman Hello, I am new to REDHAWK. Could you please help me on how to install all jtrs IDL interfaces into REDHAWK Target SDR. Thank you.
The text was updated successfully, but these errors were encountered: