Closed zimri-leisher closed 6 months ago
@bocchino we just talked about port strings. Did you have any insight here?
This issue should be fixed as of this PR: https://github.com/fprime-community/fpp/pull/321. It looks like the version of FPP being used (1.3.0) predates this PR.
Thank you! I will patch our fork with this and let you know if it fixes the problem.
From my understanding, I need to update fprime-fpp
to 2.0.2. However, when I do this, various fprime-util
commands fail because CMake scripts break because updating removes some executables from /usr/local/bin
(e.g. fpp-depend
, fpp-locate-defs
).
Is this intended behavior of switching fprime-fpp
versions? Is the only fix to update the F` version, or is there some supported way of just updating the CMake scripts?
I'm closing this because this issue is apparently already solved. I don't think we're going to update our internal fork for this fix, we will just use a new type which only has a string inside of it.
Problem Description
I have a port:
I use it in a component:
I get this error:
If I use any type other than
string
, it works (even a type with a string inside of it). If I specify the size of the string, it still doesn't work.When I move the port out of the module like so:
And use it without the prefix like so:
The component compiles. My guess is this is a bug in the autocoder, forgetting to add a
ports::
prefix to thesetIntVarPortStrings::StringSize80
type.Context / Environment
Execute
fprime-util version-check
and share the output.