Re: [pcre-dev] Current state of cmake support

George Shimanovich schrieb:
>> There's no reason to not use absolute paths at all.
> We need to have reproducible build of pcre/pcrecpp using generated
> workspace and projects. Rebuilding workspace and project files each time
> the root path changes complicates procedure unnecessarily. Also some of
> the definitions are missing in generated config.h (see my post in ' More
> Windows Building Woes').
>
> I assume that CMAKE_USE_RELATIVE_PATHS is included to support exactly
> such cases. If that option does NOT work on Windows please let me know
> so that I could avoid trying to do what is not supported.
>
cmake 2.5 doc:

CMAKE_USE_RELATIVE_PATHS
Use relative paths (May not work!).

If this is set to TRUE, then the CMake will use relative paths between
the source and binary tree. This option does not work for more
complicated projects, and relative paths are used when possible. In
general, it is not possible to move CMake generated makefiles to a
different location regardless of the value of this variable.

It's completly wrong to move generated files around (or to another
computer) as nobody can't be sure that all works exactly the same like
in the former location.



No more comments on this, if you need it, read cmake ml and ask them for
help.
Christian