incubator-celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roddie Kieley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (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 01:06:20 GMT

     [ https://issues.apache.org/jira/browse/CELIX-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Roddie Kieley updated CELIX-73:
-------------------------------

    Attachment: CELIX-73.patch

CELIX-73.patch is a quick fix that reverts the #include statements so that the cmake ${CUINT_INCLUDE_DIR}
in celix/utils/CMakeLists.txt as used to generate the Celix.xcodeproj file creates a buildable
project.


However, from my pov it is not not really a great fix as

<CUnit/Automated.h>
provides more information as to the origin and purpose of the header than
<Automated.h>
                
> 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'
via
> <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

Mime
View raw message