Skip to content
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.

Sign up for GitHub

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

Jump to bottom

player: command line argument processing is broken on systems with boost 1.59 or greater #308

Closed
juanrubio opened this issue Apr 18, 2017 · 0 comments
Closed

player: command line argument processing is broken on systems with boost 1.59 or greater #308

juanrubio opened this issue Apr 18, 2017 · 0 comments
Assignees
@juanrubio
Labels
bug
Milestone
v.0.8.0

Comments

@juanrubio
Copy link
Member

juanrubio commented Apr 18, 2017 •
edited
Loading

'implicit_option' changed its behavior in boost 1.59 so that --option_name option_value no longer works. See:

A workaround might be possible

NOTE: argument processing works if it is specified in the following manner:

  • --option=value
  • -ovalue
@juanrubio juanrubio added the bug label Apr 18, 2017
@juanrubio juanrubio added this to the v.0.8.0 milestone Apr 18, 2017
@juanrubio juanrubio self-assigned this Apr 18, 2017
@juanrubio juanrubio changed the title player: command line arguments processing is broken on systems with boost 1.59 or greater player: command line argument processing is broken on systems with boost 1.59 or greater May 18, 2017
juanrubio pushed a commit that referenced this issue Aug 1, 2017
player: Workaround for 'implicit_option' behavioral change introduced…
e3fa61d 
… in boost 1.59 (closes #308)
@juanrubio juanrubio mentioned this issue Oct 13, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@juanrubio juanrubio

Labels
bug
Projects
None yet
Milestone
v.0.8.0
Development

No branches or pull requests
1 participant
@juanrubio