> No more comments on this, if you need it, read cmake ml and ask them
for
help.
No, I don't need to ask for help in fixing that but I thought that
others may want to know the current state of CMAKE_USE_RELATIVE_PATHS
support on Windows.
Here it is:
-- AdditionalIncludeDirectories is only partially modified (only the
first path - see below)
-- Only some of the contained file paths are modified - shown below for
pcre.vcproj
-- It properly modifies
I am sure CMake people can fix that if they want to. Until then one will
need to replace existing absolute paths in project files with relative
paths manually (e.g. from VS) - relative to project file location. I did
just that before being told to try CMAKE_USE_RELATIVE_PATHS. Not a big
deal.
I suggest adding a note to that effect in NON-UNIX-USE.
Thanks,
- George
AdditionalIncludeDirectories="E:\builds\pcre\build;E:\builds\pcre\pcre-7
.5;"
AdditionalIncludeDirectories=".;E:\builds\pcre\pcre-7.5;"
RelativePath="pcre.h">
RelativePath="pcre_chartables.c">
RelativePath="pcre_chartables.c.rule">
-----Original Message-----
From: pcre-dev-bounces@??? [
mailto:pcre-dev-bounces@exim.org] On
Behalf Of Christian Ehrlicher
Sent: Thursday, January 17, 2008 11:25 AM
To: pcre-dev@???
Subject: 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
******************Legal Disclaimer***************************
"This communication may contain confidential and privileged material
for the sole use of the intended recipient. Any unauthorized review,
use or distribution by others is strictly prohibited. If you have
received the message in error, please advise the sender by reply
email and delete the message. Thank you."
****************************************************************
