<html 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1624386841;
mso-list-type:hybrid;
mso-list-template-ids:-1151045988 -1 68026371 68026373 68026369 68026371 68026373 68026369 68026371 68026373;}
@list l0:level1
{mso-level-start-at:2017;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style></head><body lang=HU link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Paul!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I do not quite understand your comments.</p><p class=MsoNormal><o:p> </o:p></p><ul style='margin-top:0cm' type=disc><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>Are you referring to the SFML distribution model? I am aware that deliberately forcing my end-users to ship a FindModule script sucks and I was not trying to promote that. I just said that it happens. The part where you say „emphasize that is for upstream libraries not downstream users”. How can I create a FindModule script FOR an upstream? Upstream is done. It’s compiled. Who else could the target audience of a FindModule script be, other other than a downstream user?</li><li class=MsoListParagraph style='margin-left:0cm;mso-list:l0 level1 lfo1'>How can CMAKE_PREFIX_PATH be considered desirable over the package registry? I compile something, install and, register it, done. Fire and forget. I don’t think that either specifying toolchain files or specifying CMAKE_PREFIX_PATH are better than simply specifying… nothing?</li></ul><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sorry if I am lost in translation, I’m just trying to understand.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers,</p><p class=MsoNormal>Máté</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>Feladó: </b><a href="mailto:pfultz2@yahoo.com">paul</a><br><b>Elküldve: </b>2017. szeptember 20., szerda 23:46<br><b>Címzett: </b><a href="mailto:csiga.biga@aol.com">Nagy-Egri Máté Ferenc</a>; <a href="mailto:cmake@cmake.org">Cmake Mailing List</a><br><b>Tárgy: </b>Re: [CMake] CMake tutorial on Github</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This looks good, a couple of comments:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>- A common misconception for libraries is to generate a Find module for</p><p class=MsoNormal>downstream users. You don't suggest that in the tutorial, but in the section</p><p class=MsoNormal>"Shipping Find Module scripts" it would be a good idea to emphasize that is</p><p class=MsoNormal>for upstream libraries not downstream users.</p><p class=MsoNormal>- It should mention `CMAKE_PREFIX_PATH` as a way to tell cmake where</p><p class=MsoNormal>dependencies are installed, and really should be preferred over modifying a</p><p class=MsoNormal>global "registry".</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>On Wed, 2017-09-20 at 16:36 +0200, Nagy-Egri Máté Ferenc via CMake wrote:</p><p class=MsoNormal>> Hi fellow CMakers!</p><p class=MsoNormal>> </p><p class=MsoNormal>> As part of a university course and an attempt to safeguard my time against</p><p class=MsoNormal>> all the one-to-one CMake tutorials I have held thus far, I have created a</p><p class=MsoNormal>> free CMake tutorial available here. It is fairly basic, in its current form</p><p class=MsoNormal>> is more or less just a jump-start guide. I wanted to maintain a consistent</p><p class=MsoNormal>> and modern style of scripting keeping up to date with the latest features.</p><p class=MsoNormal>> </p><p class=MsoNormal>> If you like it and have collegues that need the first push, feel free to</p><p class=MsoNormal>> point them in this direction. If you feel like contributing, or simply have</p><p class=MsoNormal>> ideas which directions to take next, I am open to both suggestions and PRs.</p><p class=MsoNormal>> I am aware that raw Github is not the best platform for such a writing, but</p><p class=MsoNormal>> it was immensely simple to fire up, I need not worry about hosting, and</p><p class=MsoNormal>> collaborating on the material is a breeze.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Do keep in mind it is an unofficial tutorial and reflects MY understanding</p><p class=MsoNormal>> of CMake, not those of its day to day developers. (I have looked at the</p><p class=MsoNormal>> codebase on one occasion when I wanted to implement a feature, but it</p><p class=MsoNormal>> would’ve required a complete overhaul of the makefile generators which I did</p><p class=MsoNormal>> not have the capacity to do. If I’ll have the time, I’ll continue working on</p><p class=MsoNormal>> it, some lessons are referred to that are currently non-existent. I do</p><p class=MsoNormal>> intend on writing them sometime.</p><p class=MsoNormal>> </p><p class=MsoNormal>> Cheers,</p><p class=MsoNormal>> Máté</p><p class=MsoNormal>> </p><p class=MsoNormal>> -- </p><p class=MsoNormal>> </p><p class=MsoNormal>> Powered by www.kitware.com</p><p class=MsoNormal>> </p><p class=MsoNormal>> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.o</p><p class=MsoNormal>> rg/Wiki/CMake_FAQ</p><p class=MsoNormal>> </p><p class=MsoNormal>> Kitware offers various services to support the CMake community. For more</p><p class=MsoNormal>> information on each offering, please visit:</p><p class=MsoNormal>> </p><p class=MsoNormal>> CMake Support: http://cmake.org/cmake/help/support.html</p><p class=MsoNormal>> CMake Consulting: http://cmake.org/cmake/help/consulting.html</p><p class=MsoNormal>> CMake Training Courses: http://cmake.org/cmake/help/training.html</p><p class=MsoNormal>> </p><p class=MsoNormal>> Visit other Kitware open-source projects at http://www.kitware.com/opensourc</p><p class=MsoNormal>> e/opensource.html</p><p class=MsoNormal>> </p><p class=MsoNormal>> Follow this link to subscribe/unsubscribe:</p><p class=MsoNormal>> http://public.kitware.com/mailman/listinfo/cmake</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>