Skip to content
This repository was archived by the owner on Aug 5, 2022. It is now read-only.

Conversation

@krocard
Copy link
Contributor

@krocard krocard commented Feb 4, 2015

When compiling swig generated files, the CXX compiler
flag list included -v. This leaded to unnecessary log
output during compilation. =>_Remove the flag.

Some cmake command were in upper case.

@makohoek
Copy link
Contributor

👍

@dawagner
Copy link
Contributor

👎 It breaks:

swig error : Unrecognized option -Wall -Werror

see http://stackoverflow.com/questions/17043088/cmake-build-calling-swig-with-multiple-arguments

The correct version would be:

SET_PROPERTY(SOURCE pfw.i PROPERTY SWIG_FLAGS "-Wall" "-Werror")

and the current makefile is wrong too.

@krocard
Copy link
Contributor Author

krocard commented Feb 16, 2015

👎

`SET_SOURCE_FILES_PROPERTIES(pfw.i PROPERTIES SWIG_FLAGS "-v" "-Wall"
"-Werror")` sets 2 variables:
 - `SWIG_FLAGS="-v"`
 - `-Wall="-Werror"`
which is obviously not what was wanted.

Replace by `SET_PROPERTY(SOURCE pfw.i PROPERTY SWIG_FLAGS "-v" "-Wall"
"-Werror")` that only sets `SWIG_FLAGS="-v -Wall -Werror"`.

Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
When compiling swig generated files, the CXX compiler
flag list included -v. This leaded to unnecessary log
output during compilation.

Remove the flag

Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
Some cmake commands were in big case in the python
binding cmake.

As all others are in low case, put everything in low case.

Signed-off-by: Kevin Rocard <kevin.rocard@intel.com>
@krocard
Copy link
Contributor Author

krocard commented Feb 16, 2015

👍

dawagner added a commit that referenced this pull request Feb 17, 2015
Remove CXX compiler verbose flag for swig binding
@dawagner dawagner merged commit d37ca91 into intel:master Feb 17, 2015
@krocard krocard deleted the no_verbose_cxx branch February 20, 2015 14:15
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants