|Message: Re: Trouble setting up sim based on example B1||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
On Thu, 31 Jan 2013 20:16:39 GMT, Philip McGeachy wrote: > ... > which I assume is because it did not include the header files which I > had placed in the source folder for the building of the solution. One > thing I did notice was that the header files were written in visual > studio C++ and I noticed that they ended with a '.h' whereas the > CMakelists.txt which I copied from B1 says to include header files from > "include" folder with ".hh". Perhaps this may be a possible cause for > why these header files aren't getting included in the solution from the > CMAKE building of the visual studio solution. If anyone has any input > into this matter it would be greatly appreciated.
Yep, that's exactly the problem :-). If you have a mix of header extensions, just add the required globbing expression(s), otherwise just change "hh" to "h"
You should be o.k. in this case just to rebuild in VS because the solution will spot that the CMake script has changed and rerun CMake.