-
Notifications
You must be signed in to change notification settings - Fork 68
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
Routable metadata #545
Routable metadata #545
Changes from all commits
711080c
cf28cae
63ae453
32b1c05
43c8739
a705342
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,8 +20,8 @@ typedef unsigned int IvpMsgFlags; | |
#define IvpMsgFlags_RouteDSRC 0x01 | ||
|
||
typedef struct IvpDsrcMetadata { | ||
int channel; | ||
int psid; | ||
int channel; | ||
} IvpDsrcMetadata; | ||
|
||
typedef struct IvpMessage { | ||
|
@@ -64,7 +64,7 @@ typedef enum { | |
*/ | ||
IvpMessage *ivpMsg_create(const char *type, const char *subtype, const char *encoding, IvpMsgFlags flags, cJSON *payload); | ||
|
||
IvpMessage *ivpMsg_addDsrcMetadata(IvpMessage *msg, int channel, int psid); | ||
IvpMessage *ivpMsg_addDsrcMetadata(IvpMessage *msg, int psid, int channel); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is there a reason we reversed these and can we ensure this does not have any unintentional impacts. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @paulbourelly999 Did it to match the changes made here: Did some quick tests with SPaT, MAP, PSM, and TIM to make sure they were still getting the right PSIDs set |
||
|
||
/*! | ||
* Creates a new IvpMessage from a json string. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this ${numCPU}? Whese is this env variable from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The env is for using the number of cores available on the local machine. This allows for building in parallel. Since we're using Ubuntu as the docker image, this command to get the env variable will always work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have a link explain how this command "make -j${numCPU}" allow building in parallel. Sorry, I have not seen this before and am curious how this works. Also if we are running this inside a base image ubuntu, how does that get the host machine hardware specs, like num of CPUs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep! Section 5.4 here: https://www.gnu.org/software/make/manual/make.html#Parallel
or run: make --help and you'll see a short description there
Yeah, it's still linked to the host machine, so it's able to find the number of cores available. Then this would run one job per core.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, in section 5.4:
If there is nothing looking like an integer after the ‘-j’ option, there is no limit on the number of job slots.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, numCPU set by
numproc