[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 305094] KDevelop crashes on CMake configuration => specific CMake macro ?
From: Nicolas SAUBAT <nicolas.saubat () imag ! fr>
Date: 2012-08-28 9:32:25
Message-ID: bug-305094-40295-hUIuNEaWTB () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=305094
Nicolas SAUBAT <nicolas.saubat@imag.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDSINFO
Resolution|--- |FIXED
--- Comment #1 from Nicolas SAUBAT <nicolas.saubat@imag.fr> ---
Hi agin,
I've been surprised not to have any answer to this post. Did I miss something
in the edition of the bug, or you guys were on holidays ?
Nevertheless, I've fixed the bug with my team, not knowing exactly why.
Here is how we did, hoping this will help someone (or someone can help us
understand this bug).
In a CMakeLists.txt file we used the CMake command :
add_subdirectory() for every subdirectories in a specific order (for dependance
purpose). We add 9 subdirectories this way, each of them including a
CMakeLists.txt file.
Replacing these "add_subdirectory()" commands with a list and a loop accross it
# get all subdirectories in a variable
get_subdirectories(COMPONENTS_LIST)
# Add subdirectories in CMake project
foreach(COMPONENT_NAME ${COMPONENTS_LIST})
add_subdirectory(${COMPONENT_NAME})
endforeach()
does the same (only the order changes), but no more segmentation fault in our
case.
Hope this will help, bye.
--
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic