-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add a C++ test outline #2
base: main
Are you sure you want to change the base?
Conversation
That is interesting, I hadn't actually tried to use it yet so this is good to know. Depending on how likely we are to use this (c++/rust) it might be good to look at it more closely now rather than later given how closely the yaml file and the actual code is generated. By that I mean, a significant refactor of the yaml code would mean a significant rewrite of the access code. For now, I'm going to work on getting all of the yaml code written for the ms, with testing code, then if we need to make large changes they can be done at that point before really diving in to the API code. I look forward to results of your investigation, thanks for this. |
I've approved the workflow (not sure it didn't work by default) so it will now run - thanks for this addition! |
Thanks, this is on my radar. |
The github action now installs cmake, the c++ compiler and katai-struct-compiler correctly. However, the generation of the cpp files now fails on master. |
@sjperkins I will try and take a look today, things on main are constantly in flux so this will happen often. If it helps, once it is compiling again I'll make a development branch so you can have a working main for your purposes. |
No pressure from my side, I thought it was important to at least get the github action to call katai-struct and attempt a compile. |
@jrhosk @astrofrog I took the work done in 6c35a60 a bit further here by building a C++ test case outline.
There are some failures when actually compiling the generated C++.
I'm just pushing this up in the hopes that it'll be useful, rather than any expectation that this needs to be dealt with in the near or even medium term: It's just good to know there might be bumps in the road.
I might some time to dig more on my side as I haven't found time to understand the interaction between the generated kaitai C++ and the compiler.
Just compiling the generated rust would also be valuable IMO.