-
Notifications
You must be signed in to change notification settings - Fork 0
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
Allowing not to build param: this will clean up any logger of any lib… #30
Conversation
…rary built using scarab (if desired)
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.
These changes do not properly account for the dependencies between the different optionally-built parts of scarab. If we're going to make param optional, we really should have a block of the CMakeLists.txt file that handles the logic of the dependencies. The dependencies are that each of the codecs requires param, and authentication requires the JSON codec.
Adding extra logic to handle the dependencies: authentication depends on codec_json which depends on param |
…am module to the right place.
…st_yaml and test_configurator
…urns on and off the option to use command-line JSON in configurator.
… into feature/no_param_builder # Conflicts: # library/CMakeLists.txt
…ld options and build option dependencies. CMakeLists.txt updated to require that dependent options be set correctly.
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.
Looks good now
…rary built using scarab (if desired).
Other libraries generally don't use the factories, but codec factories get registered anyway, leading to an useless verbosity.
Adding an option not to build param (which is responsible for this registration) has been added.
Basically, this makes Cicada loading less verbose: from
to