Jump to content
  • Advertisement

abigagli

Member
  • Content Count

    0
  • Joined

  • Last visited

Community Reputation

124 Neutral

About abigagli

  • Rank
    Newbie
  1. Great addition to an already great article. These latest cmake features are really great and simplify things a lot. If anyone's interested, I've created a very simple folder structure with relevant CMakeLists.txt files and sample code that implements most of what's discussed in this series. Just a note: I mainly work on OSX so this is a bit biased towards clang/libc++   You can check it out at https://github.com/abigagli/CMakeEnvironment
  2. Well, I'm just saying that after a PROJECT (<MYLIBNAME>) directive, it seems like cmake makes the <MYLIBNAME>_SOURCE_DIR variable defined to point where sources for that project are, so if <MYLIBNAME>'s includes are in a well defined relative path from its sources, you can get a valid pointer to their location everywhere by just using such variable e.g. <MYLIBNAME>_SOURCE_DIR/../Includes if there's an "Includes" folder at the same level where a Sources folder is. Hope this clarifies my idea a bit, and looking forward parts >=5 for additional great content!
  3. Hi, very interesting series, and really useful as I'm in the process of moving to CMake for a couple of projects I'm currently working on. First, just a typo I suspect, as you say that all tests should pass, but the code for CMakeEnvironment/Libraries/Math/Tests/TestConstruction.hpp always uses test0.X(), test0.Y(), test0.Y() in the EXPECT_EQ clauses, even when the object under test is test1x, test1y, test1z[/size]? Second, regarding the problem of letting know to the upper levels the proper INCLUDE_DIRECTORIES,  how does it sound to have a PROJECT(libname) directive in each library and then in the root CMakeLists.txt have something like INCLUDE_DIRECTORIES(${libname_SOURCE_DIR/<where_are_the_includes>})? Of course this doesn't work for the external libraries, but I see it as a cleaner solution for in-project libraries. What do you think?[/size]
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!