Skip to content

Conversation

@Cantonplas
Copy link
Contributor

Works correctly, now when you build the proyect it will create the packets and orders from your board.
You need to change the board name on the cmake tho

@Cantonplas Cantonplas changed the title Fw 301/execute code gen on cmake Fw 301/execute code gen on cmake (Now working) Sep 1, 2025
Copy link
Contributor

@jorgesg82 jorgesg82 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add all generated code in a .gitignore

oganigl
oganigl previously approved these changes Sep 22, 2025
Copy link
Contributor

@oganigl oganigl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me looks good, I just looked over it.

Copy link
Contributor

@jdmarmen jdmarmen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great job, just one thing, as you already generate the function definitions for the callbacks in the orders I would also consider to generate the flag for each order. We always use those callbacks only to change the value of the flag, so rn the user also needs to define that flag and its also a repetitive thing, what do you think @jorgesg82 ?

Co-authored-by: Jose D. <145350079+jdmarmen@users.noreply.github.com>
Copy link
Contributor

@jdmarmen jdmarmen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've seen on the template ADJ that was used to test this that you asign a socket to each packet on packets.json , that's fine as we can have different datagram sockets, but, imo that should also be done with the orders, as you can send the same tcp order to different sockets. Am i missing something??

@Cantonplas
Copy link
Contributor Author

I've seen on the template ADJ that was used to test this that you asign a socket to each packet on packets.json , that's fine as we can have different datagram sockets, but, imo that should also be done with the orders, as you can send the same tcp order to different sockets. Am i missing something??

The added selection for udp sockets is because its needed to use socket->send_packet(packet), but with the use of Orders it is not needed to specify the tcp socket its coming from. Maybe im wrong but thats why its not included or specified

Copy link
Contributor

@oganigl oganigl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me it's fine, check the comment

@jorgesg82 jorgesg82 merged commit bf3b41c into main Jan 25, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants