[Insight-developers] SimpleITK - Lua on Snow Lepard

[Williams, Norman K]

We already build Swig in BRAINS3 with ITK 3.2x, and configure CableSwig to
use our built 2.0.1 Swig in preference to the system Swig.  I think I sent
Gaetan the ExternalProject mumbo-jumbo necessary to do this, I can

Fun fact about CableSwig: It builds it's own Swig, but it doesn't actually
use it if there's a system install of Swig.



On 3/22/11 4:46 PM, "Gaëtan Lehmann" <gaetan.lehmann at jouy.inra.fr> wrote:

>
>We are planning to build swig with a cmake external project for
>wrapping.
>This might be interesting for simpleitk too.
>
>Gaëtan
>
>
>Le 22 mars 11 à 17:00, Bradley Lowekamp a écrit :
>
>> Dan,
>>
>> I have also had several other error with TCL, and Ruby. I think the
>> problem is with swig 1.3 that comes with Snow Lepoard. I upgraded to
>> swig 2.0.2, and everything went away.
>>
>> I am thinking that SimpleITK may just require swig 2.0.x+.
>>
>> Brad
>>
>> On Mar 22, 2011, at 11:48 AM, Daniel Blezek wrote:
>>
>>> Brad,
>>>
>>>   Can you make this a Jira issue?
>>>
>>> Thanks,
>>> -dan
>>>
>>>
>>> On 3/21/11 8:37 AM, "Bradley Lowekamp" <blowekamp at mail.nih.gov>
>>> wrote:
>>>
>>>> Dan,
>>>>
>>>> I have always gotten the following error when I turn on wrapping
>>>> for Lua on my macs:
>>>>
>>>> /build/SimpleITK/Wrapping/SimpleITKLUA_wrap.cxx:711:20: error:
>>>> malloc.h: No such file or directory
>>>>
>>>> Now, I can hack the file to refer to stdlib.h, or hack:
>>>>
>>>> /usr/share/swig/1.3.31/lua/luarun.swg
>>>>
>>>> to include the same. But these are both hacks in a bad way. I see
>>>> that you are wrapping Lua on you dashboard machines. Are you using
>>>> the same version of swig that comes with the OS, or a more recent
>>>> version?
>>>>
>>>> I also get some funky error when trying to wrap for TCL as well.
>>>>
>>>> Brad
>>>>
>>>>
>>>> ========================================================
>>>>
>>>> Bradley Lowekamp
>>>>
>>>> Lockheed Martin Contractor for
>>>>
>>>> Office of High Performance Computing and Communications
>>>>
>>>> National Library of Medicine
>>>>
>>>> blowekamp at mail.nih.gov
>>>>
>>>>
>>>
>>> --
>>> Daniel Blezek, PhD
>>> Medical Imaging Informatics Innovation Center
>>>
>>> P 127 or (77) 8 8886
>>> T 507 538 8886
>>> E blezek.daniel at mayo.edu
>>>
>>> Mayo Clinic
>>> 200 First St. S.W.
>>> Harwick SL-44
>>> Rochester, MN 55905
>>> mayoclinic.org
>>> "It is more complicated than you think." -- RFC 1925
>>
>> _______________________________________________
>> 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.html
>>
>> 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
>
>--
>Gaëtan Lehmann
>Biologie du Développement et de la Reproduction
>INRA de Jouy-en-Josas (France)
>tel: +33 1 34 65 29 66    fax: 01 34 65 29 09
>http://voxel.jouy.inra.fr  http://www.itk.org
>http://www.mandriva.org  http://www.bepo.fr
>
>_______________________________________________
>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.html
>
>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



________________________________
Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged.  If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited.  Please reply to the sender that you have received the message in error, then delete it.  Thank you.
________________________________