<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Andrew-<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">You are correct that it was a Windows issue, not a CMake issue. See the post I made about two hours before yours.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The problem isn’t the alphabetic ordering, though. Is the “type” of environment variable. There are two types, “expandable string” and “string”. (There are
other types for other general registry values, but env vars can only be of these two types.) It seems that if you create an env var in the normal Windows GUI, the first value you give it determines which type it is. If it contains a reference to another env
var, it’s created as “expandable string”, otherwise it’s “string”. The type of the variable isn’t updated if you update the value, so the first value you gave to BOOST_LIBRARYDIR in your test below made it type “string”, even though you modified it to reference
%BOOST_ROOT% later. You need to use RapidEE (<a href="http://www.rapidee.com/en/about">http://www.rapidee.com/en/about</a> ) to change the type of an env var, since the Windows GUI doesn’t even indicate that there are two types.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Chris<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Andrew Maclean [mailto:andrew.amaclean@gmail.com]
<br>
<b>Sent:</b> Tuesday, August 12, 2014 6:57 PM<br>
<b>To:</b> cmake@cmake.org; Chris Volpe ARA/SED; Lucas.Pettey@engilitycorp.com<br>
<b>Subject:</b> Re: [CMake] Possible bug in environment variable expansion?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">I only define:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">BOOST_ROOT=C:\local\boost_1_56_0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">BOOST_LIBRARYDIR=C:\local\boost_1_56_0\lib64-msvc-12.0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">and this works Ok.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">This will not work:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">BOOST_LIBRARYDIR=%BOOST_ROOT%\lib64-msvc-12.0<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">If you go to a command prompt and type "set" you will see that %BOOST_ROOT% is not expanded. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">So this is a Windows issue, not a CMake issue.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The only clue I have is that Microsoft expands these variables in order and since BOOST_ROOT is ordered after BOOST_LIBRARYDIR the expansion does not happen.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> Andrew<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Aug 13, 2014 at 5:37 AM, <<a href="mailto:cmake-request@cmake.org" target="_blank">cmake-request@cmake.org</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Send CMake mailing list submissions to<br>
<a href="mailto:cmake@cmake.org">cmake@cmake.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://public.kitware.com/mailman/listinfo/cmake" target="_blank">
http://public.kitware.com/mailman/listinfo/cmake</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cmake-request@cmake.org">cmake-request@cmake.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cmake-owner@cmake.org">cmake-owner@cmake.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of CMake digest..."<br>
<br>
Today's Topics:<br>
<br>
1. Windows RC files with Ninja (Miller, Frank)<br>
2. Re: Possible bug in environment variable expansion?<br>
(Chris Volpe ARA/SED)<br>
<br>
<br>
---------- Forwarded message ----------<br>
From: "Miller, Frank" <<a href="mailto:FMiller@sjm.com">FMiller@sjm.com</a>><br>
To: CMake MailingList <<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
Cc: <br>
Date: Tue, 12 Aug 2014 16:44:03 +0000<br>
Subject: [CMake] Windows RC files with Ninja<br>
Greetings,<br>
<br>
I tried to move from 2.8 to 3.0.1 today and I'm experiencing an issue with RC files. Looks like a simple problem but I would be baffled if I'm the first to experience this so I expect I have some kind of configuration issue. Here is the offending snippet in
the rules.ninja file:<br>
<br>
rule RC_COMPILER<br>
depfile = $DEP_FILE<br>
deps = gcc<br>
command = "" RC $in "$DEP_FILE" $out "" "c:/Program Files (x86)/Microsoft Visual Studio 12.0/VC/bin/cl.exe" c:\PROGRA~2\WI3CF2~1\8.1\bin\x86\rc.exe $FLAGS $DEFINES /fo$out $in<br>
description = Building RC object $out<br>
<br>
If I put the path to "cmcldeps.exe" in the empty quotes on the command line, it works as expected.<br>
<br>
Does anyone else have this problem?<br>
<br>
Frank<br>
<br>
This communication, including any attachments, may contain information that is proprietary, privileged, confidential or legally exempt from disclosure. If you are not a named addressee, you are hereby notified that you are not authorized to read, print, retain
a copy of or disseminate any portion of this communication without the consent of the sender and that doing so may be unlawful. If you have received this communication in error, please immediately notify the sender via return e-mail and delete it from your
system. In order to safeguard its employee data as well as sensitive patient, customer, business, legal and other information, the company uses all lawful means, under all applicable law, to access, monitor, preserve, collect and review all communications
between employees and all other users only when, and to the extent necessary, to fulfill investigatory and other important business and legal responsibilities. By responding to this communication, or initiating additional communication with the company, you
consent to such lawful monitoring, to the extent such consent is required and valid in your local area.<br>
<br>
<br>
<br>
---------- Forwarded message ----------<br>
From: Chris Volpe ARA/SED <<a href="mailto:cvolpe@ara.com">cvolpe@ara.com</a>><br>
To: Chris Volpe ARA/SED <<a href="mailto:cvolpe@ara.com">cvolpe@ara.com</a>>, "<a href="mailto:Lucas.Pettey@engilitycorp.com">Lucas.Pettey@engilitycorp.com</a>" <<a href="mailto:Lucas.Pettey@engilitycorp.com">Lucas.Pettey@engilitycorp.com</a>>, "<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>"
<<a href="mailto:cmake@cmake.org">cmake@cmake.org</a>><br>
Cc: <br>
Date: Tue, 12 Aug 2014 19:37:47 +0000<br>
Subject: Re: [CMake] Possible bug in environment variable expansion?<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">As it turns out, something weirder is going on, and it’s not cmake’s fault, so I won’t look for a solution here, but I’ll describe the problem in case
anyone’s interested. *<b>Windows</b>* is not expanding those environment variables. First, I hacked up the installed version of FindBoost.cmake to spit out some debugging information, with the following, circa line 860:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> message(DEBUG "_ENV_BOOST_LIBRARYDIR has value <${_ENV_BOOST_LIBRARYDIR}>")</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">and then I ran configure in debug mode, which gave me the following from my extra hacked debugging output:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:red">DEBUG_ENV_BOOST_LIBRARYDIR has value <%BOOST_ROOT%/lib64-msvc-12.0></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">So, when cmake asked the OS for the BOOST_LIBRARYDIR environment variable, the OS gave it the string without expanding BOOST_ROOT. I have verified this
OS behavior by opening up a command window and using the set command: It’s not getting expanded. I’ve verified (with RapidEE) that the environment variables in question are of type “expandable string”, not “string”.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">While playing with the variables in RapidEE (a wonderful tool, BTW), I noticed two other strange things. First, I do have a couple of env vars that do
have other env var references in them, and they *<b>do</b>* get expanded in cmd.exe. Second, my PATH env var used to have embedded env vars for various things, but somewhere along the way they all got replaced in the PATH *<b>definition</b>* with their expanded
versions, so now everything in my path is now “hard coded”, so to speak. Ugh.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">So, basically, something is messed up in my system.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> CMake [mailto:<a href="mailto:cmake-bounces@cmake.org" target="_blank">cmake-bounces@cmake.org</a>]
<b>On Behalf Of </b>Chris Volpe ARA/SED<br>
<b>Sent:</b> Tuesday, August 12, 2014 12:44 PM<br>
<b>To:</b> <a href="mailto:Lucas.Pettey@engilitycorp.com" target="_blank">Lucas.Pettey@engilitycorp.com</a>;
<a href="mailto:cmake@cmake.org" target="_blank">cmake@cmake.org</a><br>
<b>Subject:</b> Re: [CMake] Possible bug in environment variable expansion?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">That’s a good thought, but unfortunately it didn’t pan out. I tried both styles, and I even tried explicitly mixing styles like this:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_LIBRARYDIR=C:/local/boost_1_55_0\lib64-msvc-12.0</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Or this:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_LIBRARYDIR=C:\local\boost_1_55_0/lib64-msvc-12.0</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">And those worked fine.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:Lucas.Pettey@engilitycorp.com" target="_blank">Lucas.Pettey@engilitycorp.com</a> [mailto:<a href="mailto:Lucas.Pettey@engilitycorp.com" target="_blank">Lucas.Pettey@engilitycorp.com</a>]
<br>
<b>Sent:</b> Monday, August 11, 2014 11:03 PM<br>
<b>To:</b> Chris Volpe ARA/SED; <a href="mailto:cmake@cmake.org" target="_blank">
cmake@cmake.org</a><br>
<b>Subject:</b> RE: Possible bug in environment variable expansion?</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Could it be something as simple as UNIX (slash /) vs Windows (backslash \) in the directory expression?
</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">When this environment variable is expanded </span><span style="font-size:11.5pt;color:black">BOOST_LIBRARYDIR=%BOOST_ROOT%\lib64-msvc-12.0,
it looks like it is converting the %BOOST_ROOT% in UNIX style and then the "\lib-msvc-12.0" is Windows. This mixture of styles may be causing a "no such directory" system error. I know on Windows systems I need to be consistent with directory styles or it
fails.</span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Lucas Pettey, PhD </span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black;background:white">HPCMP</span><span style="font-size:11.5pt;color:#005B99"> </span><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">PETTT
EQM CTA Lead</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">ERDC-DSRC OnSite </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">Vicksburg, MS</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><a href="tel:512-297-9833" target="_blank">512-297-9833</a> Mobile (preferred)</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><a href="tel:601-634-2980" target="_blank">601-634-2980</a> Office</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"><a href="mailto:lucas.pettey@engilitycorp.com" target="_blank">lucas.pettey@engilitycorp.com</a></span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div class="MsoNormal" align="center" style="text-align:center"><span style="color:black">
<hr size="2" width="100%" align="center">
</span></div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black"> CMake [<a href="mailto:cmake-bounces@cmake.org" target="_blank">cmake-bounces@cmake.org</a>]
on behalf of Chris Volpe ARA/SED [<a href="mailto:cvolpe@ara.com" target="_blank">cvolpe@ara.com</a>]<br>
<b>Sent:</b> Monday, August 11, 2014 6:25 PM<br>
<b>To:</b> <a href="mailto:cmake@cmake.org" target="_blank">cmake@cmake.org</a><br>
<b>Subject:</b> [CMake] Possible bug in environment variable expansion?</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">I am trying to build an Open Source project called PCL which uses Boost, and CMake’s ability to find the Boost libraries seems dependent on whether the
BOOST_LIBRARYDIR contains a literal path string, or whether it contains a string that incorporates the expansion of BOOST_ROOT. Here are the details:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Boost is installed from a pre-built installer in the folder C:\local\boost_1_55_0. This folder contains, among other things, a subfolder called “boost”,
which contains the headers, and a subfolder called “lib64-msvc-12.0”, which contains 64-bit libraries built with MS Visual Studio 2013. Ordinarily, CMake would like that folder to be called simply “lib”, but that’s not what the installer created, so I’m trying
to override the default with environment variables. I have the following three environment variables defined, all of which are of type “Expandable string”:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_ROOT=C:\local\boost_1_55_0</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_INCLUDEDIR=%BOOST_ROOT%</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_LIBRARYDIR=%BOOST_ROOT%\lib64-msvc-12.0</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">With these settings, CMake reports an error during the configuration process, as follows:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<span style="color:red">CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.0/Modules/FindBoost.cmake:1179 (message):<br>
Unable to find the requested Boost libraries.<br>
<br>
Boost version: 1.55.0<br>
<br>
Boost include path: C:/local/boost_1_55_0<br>
<br>
Could not find the following Boost libraries:<br>
<br>
boost_system<br>
boost_filesystem<br>
boost_thread<br>
boost_date_time<br>
boost_iostreams<br>
boost_chrono<br>
<br>
No Boost libraries were found. You may need to set BOOST_LIBRARYDIR to the<br>
directory containing Boost libraries or BOOST_ROOT to the location of<br>
Boost.<br>
Call Stack (most recent call first):<br>
cmake/pcl_find_boost.cmake:38 (find_package)<br>
CMakeLists.txt:230 (include)</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">But if change the definition of BOOST_LIBRARYDIR by replacing “%BOOST_ROOT%” with the value assigned to BOOST_ROOT, resulting in this:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">BOOST_LIBRARYDIR=C:\local\boost_1_55_0\lib64-msvc-12.0</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">the configuration succeeds. The only difference seems to be whether the “C:\local\boost_1_55_0” part of the path is specified explicitly, or obtained implicitly
with %BOOST_ROOT%. It would surprise me if this behavior were by design. Does anyone have an explanation for this?</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Thanks,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black">Chris</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-family:"Arial","sans-serif";color:black">Christopher R. Volpe, Ph.D.</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span style="font-family:"Arial","sans-serif";color:gray">Senior Scientist, Remote Sensing & Decision Analytics</span></i><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><i><span style="font-family:"Arial","sans-serif";color:gray"> </span></i><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black"><img border="0" width="168" height="60" id="_x0000_i1026" src="cid:image001.png@01CFB877.1BFA6F10" alt="Description: Description: Description: cid:image003.png@01CE888B.0167BAD0"></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#632423">NATIONAL SECURITY</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray">
| </span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#632423"> INFRASTRUCTURE
</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray"> |
</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#632423">ENERGY & ENVIRONMENT
</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:gray"> |</span></b><b><span style="font-size:8.0pt;font-family:"Arial","sans-serif";color:#632423"> HEALTH SOLUTIONS</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">Applied Research Associates, Inc.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">8537 Six Forks Road, Suite 600, Raleigh, NC 27615
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray">|</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">
</span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#632423">T
</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black"><a href="tel:919.582.3380" target="_blank">919.582.3380</a>
</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:gray">|</span><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">
</span><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:#632423">F</span></b><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black">
<a href="tel:919.582.3301" target="_blank">919.582.3301</a> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:9.0pt;font-family:"Arial","sans-serif";color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:9.0pt;color:black">Find Us Online</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://www.ara.com" target="_blank"><span style="font-size:8.0pt">www.ara.com</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="https://www.facebook.com/#!/AppliedResearchAssociates" target="_blank"><span style="font-size:8.0pt">Facebook: Applied Research Associates</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://www.linkedin.com/company/8853?trk=tyah" target="_blank"><span style="font-size:8.0pt">LinkedIn: Company Page</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://www.linkedin.com/groups/ARA-Employees-Group-4854334?trk=myg_ugrp_ovr" target="_blank"><span style="font-size:8.0pt">LinkedIn Group</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="https://twitter.com/ARA_News_Events" target="_blank"><span style="font-size:8.0pt">Twitter: ARA News</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"><a href="http://www.youtube.com/user/AppliedResearch1?feature=mhee" target="_blank"><span style="font-size:8.0pt">YouTube: Applied Research Associates</span></a></span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:black"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><br>
--<br>
<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">
http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Kitware offers various services to support the CMake community. For more information on each offering, please visit:<br>
<br>
CMake Support: <a href="http://cmake.org/cmake/help/support.html" target="_blank">
http://cmake.org/cmake/help/support.html</a><br>
CMake Consulting: <a href="http://cmake.org/cmake/help/consulting.html" target="_blank">
http://cmake.org/cmake/help/consulting.html</a><br>
CMake Training Courses: <a href="http://cmake.org/cmake/help/training.html" target="_blank">
http://cmake.org/cmake/help/training.html</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">
http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/cmake" target="_blank">http://public.kitware.com/mailman/listinfo/cmake</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <br>
___________________________________________<br>
Andrew J. P. Maclean<br>
<br>
___________________________________________ <o:p></o:p></p>
</div>
</div>
</div>
</body>
</html>