<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Eventually C++ 2017 wil have filesystem in it - just cant wait that long - If we can’t use 1.60 then we will have to use kwsys (or write our own) - does everything build with 1.60?<div class=""><br class=""></div><div class="">Bob</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Robert M. O'Bara, MEng.<br class="">Assistant Director of Scientific Computing<br class=""><br class="">Kitware Inc.<br class="">28 Corporate Drive<br class="">Suite 101<br class="">Clifton Park, NY 12065<br class=""><br class="">Phone: (518) 881- 4931</div><div class=""><br class=""></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jan 29, 2016, at 3:54 PMEST, David Thompson <<a href="mailto:david.thompson@kitware.com" class="">david.thompson@kitware.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><blockquote type="cite" class="">Personally I would be hesitant to upgrade our boost version for a<br class="">feature that shouldn't be hard to replicate.<br class=""></blockquote><br class="">Except that there are many corner cases (*cough* Windows drive letters *cough*) that make it harder than you might think to replicate.<br class=""><br class="">Also, the only reason we rely on boost is the filesystem library (and soon polygon, but that is optional). So it seems odd to implement something that a library we depend on has implemented in a later revision. If we're going to do that, then we should eliminate the boost requirement and just use it optionally for polygon. :-)<br class=""><br class=""><span class="Apple-tab-span" style="white-space:pre"> </span>David<br class=""><br class=""><blockquote type="cite" class=""><br class=""><br class=""><br class="">On Fri, Jan 29, 2016 at 2:58 PM, David Thompson<br class=""><<a href="mailto:david.thompson@kitware.com" class="">david.thompson@kitware.com</a>> wrote:<br class=""><blockquote type="cite" class=""><blockquote type="cite" class="">What about using kwsys::RelativePath ?<br class=""></blockquote><br class="">SMTK does not require VTK (which is the only place we would inherit kwsys).<br class=""><br class="">I would rather make the relative path thing optional if you have an older boost than add another dependency.<br class=""><br class=""> David<br class="">_______________________________________________<br class="">Smtk-developers mailing list<br class=""><a href="mailto:Smtk-developers@smtk.org" class="">Smtk-developers@smtk.org</a><br class="">http://public.kitware.com/mailman/listinfo/smtk-developers<br class=""></blockquote></blockquote><br class=""></div></blockquote></div><br class=""></div></body></html>