[ITK-dev] Missing IO factories when building without cmake
Bradley Lowekamp
blowekamp at mail.nih.gov
Tue Apr 1 14:53:59 EDT 2014
Perhaps my initial question wasn't clear.
Is the ITK FAQ[1] the best place to comprehensively document this common question or more up to date place?
Brad
[1] http://www.itk.org/Wiki/ITK/FAQ
On Apr 1, 2014, at 2:48 PM, Matt McCormick <matt.mccormick at kitware.com> wrote:
> +1. Bill's fix was the best one I have seen implemented.
>
> On Tue, Apr 1, 2014 at 2:39 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>> We need to do something to help the users. There are 42 messages (not
>> including threads) on the users list. Typically, after a few
>> responses, we ask "Are you using cmake to configure your project?" Our
>> suggested solutions are not consistent. My patch provided an
>> explanation of the most probable cause (not using cmake) and a
>> solution (register the IO's you need). These questions seem to be from
>> users that are creating apps, not users of apps that someone has
>> created.
>>
>> Bill
>>
>>
>> On Tue, Apr 1, 2014 at 11:31 AM, Matt McCormick
>> <matt.mccormick at kitware.com> wrote:
>>> On Tue, Apr 1, 2014 at 2:04 PM, Jim Miller <millerjv at gmail.com> wrote:
>>>> Is there a way at build time whether we could whether an executable does not have any imageio factories linked in?
>>>
>>> Nope - the issue is caused by initialization that occurs at runtime.
>>> The ImageIO classes are linked in.
>>>
>>> Matt
>>
>>
>>
>> --
>> Unpaid intern in BillsBasement at noware dot com
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.php
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
More information about the Insight-developers
mailing list