[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 200216] Parser does not handle #include_next correctly
From:       Armin Berres <trigger () space-based ! de>
Date:       2009-07-15 22:41:38
Message-ID: 20090715224138.DEEFC17C08 () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=200216





--- Comment #5 from Armin Berres <trigger space-based de>  2009-07-16 00:41:37 ---
Ohohoh. I found the real issue. While trying to copy some code to create a
little sample project I stumbled about this in my cmake code:

IF(${Boost_INCLUDE_DIR} STREQUAL "/usr/include")
  ADD_DEFINITIONS(-DBOOST_TR1_DISABLE_INCLUDE_NEXT)
ENDIF()

The problem is, that if boost is installed to /usr/include #include_next cannot
work and if BOOST_TR1_DISABLE_INCLUDE_NEXT is defined boost uses a workaround.
Is it possible, that Kdevelop does not get, which defines are set in cmake? And
if this is the case, is there a way, how I can manually set project wide
defines, the parser honors?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]