Skip to content

Conversation

@tomlogic
Copy link
Contributor

At what point is it safe to merge dev back to master and tag a release?

I made a lot of changes to dev, including cleaning up code, merging a pinprocfw bug on P3, adding a feature used in MPF and removing the yaml-cpp dependency.

jabdoa2 and others added 30 commits February 10, 2016 18:15
… from address 3, but P3-ROC is bits 11:8, and P-ROC is bits 7:4.
Can now actually set these with the -D command line option.
Quiets a compiler warning, and matches the `file_board_id` declaration.
When building in MSYS2/MinGW64, I was missing multiple DLLs necessary
to run the EXE files from a command prompt.
Previously we'd fail to call PRDelete(), which may have been causing
some of my problems with attempting to re-connect to the P-ROC.
I assume PRDelete() closes out the connection in some way.
Merge outstanding commits to `dev`
`pinproctest` now takes machineType as it's command-line parameter.
Compiler warnings showed we were overflowing arrays sized for
kPRDriverGroupsMax.
`combinedVersionRevision` is a 32-bit value.  This API isn't exposed in
the public pinproc.h header, so it's safe to make this change.
Expose some useful values for code that interfaces with libpinproc.
Includes check to limit accelerometer-related code to P3-ROC since
it fails on the P-ROC (which doesn't have an accelerometer).
Added for yaml-cpp, which is no longer a dependency for pinproctest.
This is a reasonable requirement.  It allows removal of two OLD policies
and gives us consistent behavior for relative link directories.
While case-insensitive compare of the machine type passed on the
command line would be nice, the function to do so has different names
on different platforms, and its behavior may be impacted by the user's
locale setting.
By setting stdout to unbuffered, the user always sees our output and we
can eliminate the fflush() calls sprinkled throughout the programs.
@tomlogic
Copy link
Contributor Author

Thoughts, @gstellenberg @jabdoa2 @preble ?

Maybe if I can get a P3-ROC and resolve the pinprocfw issue we could release a 2.1?

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