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
Enable meta examples when ENABLE_TESTING is OFF. #3611
Conversation
examples/meta/cpp/CMakeLists.txt
Outdated
|
||
# Suppress unused variable warnings | ||
# if we are not testing the meta_examples | ||
IF (NOT ENABLE_TESTING) |
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.
yes I think I like this
examples/meta/cpp/CMakeLists.txt
Outdated
@@ -45,3 +53,10 @@ ENDFOREACH() | |||
add_custom_target(build_cpp_meta_examples ALL | |||
DEPENDS ${GENERATED_CPP_EXAMPLES} | |||
COMMENT "Compiled generated cpp examples") | |||
|
|||
IF (NOT ENABLE_TESTING) | |||
MESSAGE( |
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.
maybe you can put that to the place where you set the flags rather than down here?
Also, the indentation is a bit weird
examples/meta/CMakeLists.txt
Outdated
@@ -27,18 +27,25 @@ FOREACH(META_EXAMPLE ${META_EXAMPLES}) | |||
LIST(APPEND EXAMPLE_LISTINGS ${CMAKE_CURRENT_BINARY_DIR}/r/${BASENAME}.R) | |||
LIST(APPEND EXAMPLE_LISTINGS ${CMAKE_CURRENT_BINARY_DIR}/lua/${BASENAME}.lua) | |||
|
|||
# Set generate.py flags |
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.
indentation not respecting the previous one, makes reviewing much harder for me btw
This is not the solution that I mentioned in #3553 Also, the warning thing with the flag, could you put that into another patch to separate concerns here? |
Hi @karlnapf, The The patch behaviour is:
I thought this was the best approach to solve this problem and I understood this was the way to proceed when I read the issue you made, but probably I didn't catch your idea, my bad :). Secondly, I wouldn't like to split the unused variable warnings into another patch because we have unused variable warning only when we produce meta example code that has not However, if you prefer to have two separate patch I will gladly create another one. :) By the way, I moved the unused variable warning and its message close together (since it is more logical as you pointed out), but I don't understand why it shows that bad indentation (I am using tab characters tabsize 4 as specified by yours developer guide). UPDATE 13/02/2014: I had to move the unused variable warning message to its previous location because it was behaving too verbosely (see this: http://pastebin.com/MF5RDjce). |
ec6437f
to
c850472
Compare
Thanks for the good explanation :) I agree with the variable stuff. I should have realised this but I think I looked at this on my phone... Very nice work! Merging! |
Enable meta examples when ENABLE_TESTING is OFF.
Resolve issue #3553