Yes, I was aware of this, but now I double checked it. I built
everything from scratch. The option has the value "2,3" at both level.
My config is this:
set(MITK_INITIAL_CACHE_FILE
"${CMAKE_CURRENT_BINARY_DIR}/mitk_initial_cache.txt")
file(WRITE "${MITK_INITIAL_CACHE_FILE}" "
set(ITK_USE_REVIEW ON CACHE INTERNAL \"Build algorithms that are
candidates to be included in the Toolkit.\")
set(MITK_ACCESSBYITK_DIMENSIONS:STRING "2,3,4" CACHE INTERNAL \"List
of dimensions used in AccessByItk and InstantiateAccessFunction
macros\")
set(MITK_BUILD_TUTORIAL OFF CACHE INTERNAL \"Build the MITK tutorial\")
set(MITK_BUILD_org.mitk.gui.qt.segmentation ON CACHE INTERNAL \"Build
the segmentation plugin\")
set(MITK_BUILD_org.mitk.gui.qt.measurement ON CACHE INTERNAL \"Build
the measurement plugin\")
set(MITK_BUILD_org.mitk.gui.qt.imagestatistics ON CACHE INTERNAL
\"Build the image statistics plugin\")
set(MITK_BUILD_org.mitk.gui.qt.volumevisualization ON CACHE INTERNAL
\"Build the volume visualization plugin\")
set(MITK_DOXYGEN_BUILD_ALWAYS OFF CACHE INTERNAL \"Always build the
MITK documentation when building the default target\")
set(MITK_DOXYGEN_GENERATE_QCH_FILES ON CACHE INTERNAL \"Use doxygen to
generate Qt compressed help files for MITK docs\")
")
Is it correct? Or shall I remove the ":STRING", maybe?
Thanks,
Miklos
On Thu, Dec 8, 2011 at 10:26 AM, Sascha Zelzer
<[email protected]> wrote:
> Hi Miklos,
>
> Your mitk_initial_cache.txt file is used as the argument to the "cmake -C
> <initial-cache>" call. As such, the cache values are only considered by
> CMake if there is no CMakeCache.txt file yet. Are you sure you tried your
> option with an empty MITK build directory?
>
> - Sascha
>
>
> On 12/08/2011 10:05 AM, Miklos Espak wrote:
>>
>> Hi,
>>
>> I have an external application, and I customize some MITK settings by
>> writing values to the mitk_initial_cache.txt file from the
>> CMakeList.txt file of the project.
>>
>> This works at the most cases, but for the MITK_ACCESSBYITK_DIMENSIONS
>> variable not. The reason can be that this option exists also at the
>> superbuild level, so probably it is overwritten with that value.
>>
>> Is is possible to remove the option from the superbuild level, like it
>> was made with the options to enable plugins?
>>
>> Thanks,
>> Miklos
>>
>>
>> ------------------------------------------------------------------------------
>> Cloud Services Checklist: Pricing and Packaging Optimization
>> This white paper is intended to serve as a reference, checklist and point
>> of
>> discussion for anyone considering optimizing the pricing and packaging
>> model
>> of a cloud services business. Read Now!
>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>> _______________________________________________
>> mitk-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
>
------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
