celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Broekhuis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CELIX-73) CUint include directory used directly then header included via <CUint/Automated.h> can't be found in Xcode
Date Thu, 27 Jun 2013 06:48:20 GMT

    [ https://issues.apache.org/jira/browse/CELIX-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694529#comment-13694529

Alexander Broekhuis commented on CELIX-73:


This change wasn't fully intended, but looking at all the CUnit examples etc, I think using
CUnit/Automated.h makes more sense.

Regarding the patch, a better workaround is to simply change the include paths in the cmake
gui (ccmake . in the build directory, and then the line CUNIT_INCLUDE_DIR.

The actual problem is in the FindCUnit.cmake file, it searches in the */include/CUnit directories
instead of only */include. I'll try to make a fix for this today.
> CUint include directory used directly then header included via <CUint/Automated.h>
can't be found in Xcode 
> -----------------------------------------------------------------------------------------------------------
>                 Key: CELIX-73
>                 URL: https://issues.apache.org/jira/browse/CELIX-73
>             Project: Celix
>          Issue Type: Bug
>         Environment: OSX 10.7.5, Xcode 4.5.1
>            Reporter: Roddie Kieley
>         Attachments: CELIX-73.patch
> When testing CELIX-72 from clean checkout of trunk, build no longer works in Xcode
> for at least four targets:
> * hash_map_test
> * hash_map_test_hash
> * array_list_test
> * linked_list_test
> Initial check show's that files such as 'linked_list_test.c' now include CUnit's 'Automated.h'
> <CUnit/Automated.h>
> vs. the previous
> <Automated.h>
> However, the 'Header Search Paths' still shows '/opt/local/include/CUnit'.
> Changing this to '/opt/local/include' causes the target to build successfully.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message