Thanks again Eric for the update... I pulled the cpack source code and
started looking through it and came to the same conclusion. Additionally
I ran into a message on the boards about the PACKAGE_SOURCE not being
included in the cmake build. Everything started making sense shortly
after I discovered the other type of build (binary versus source CPack
projects) and I have now added the necessary code to not install source
if desired.
-D
Eric Noulard wrote:
2009/3/9 Eric Noulard <eric.noul...@gmail.com>:
My mistake, I've cut the wrong part, sorry about that
CPACK_SOURCE_FILES was meant to be CPACK_IGNORE_FILES
you want to ignore files in BINARY package so the var to use is
CPACK_IGNORE_FILES
when you want to ignore files in a SOURCE pacakge then you should use
CPACK_SOURCE_IGNORE_FILES
I should stop writing totally wrong advices for this for a while.
I did answer without testing because I thought I already did it.
Now that I took time to test, I'm now pretty sure my memory was flawed.
I think you may not ignore files in a BINARY packager, you may seem
to only be able to do it for a SOURCE one.
The binary CPack packager do take *all* what is installed by
INSTALL(...) command
(put aside the COMPONENT stuff which enables you to select part of it
when the CPack generator supports it).
Thus I would say that if you want to "filter" something put by INSTALL
you'll have to:
- avoid installing it alltogether
- file a feature request to CPack
Now I'm gonna avoid "fast-answer" for a while because my last 2 were
totally wrong
sorry about that.
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
