[Rtk-users] Installing SimpleRTK on 64-bit windows

[Simon Rit]

Hi Daniel,
Please use the mailing list. There might be better users than me to
answer your question (particularly this one!).
I'm not an expert in Python and Windows but it seems that it's not
looking for the module in the install directory of the SimpleRTK
module. Have you set PYTHONPATH to look at the install directory of
SimpleRTK? Have you set the correct python include and libraries in
the compilation of RTK?
Kind regards,
Simon

On Fri, Jan 27, 2017 at 9:03 PM, Markel, Daniel
<daniel.markel at rmp.uhn.ca> wrote:
> Hi Simon,
>
>
>
>                   I’m trying to install simpleRTK  on my laptop running
> windows 7 64-bit and having great difficulty. I managed to build ITK
> properly and create a 64-bit build of RTK with simpleRTK without any errors
> using visual studio 2015. I’m also running anaconda which has Python 3.5.1
> built in. However after building it and installing using the ‘python
> PythonPackages/setup.py install’ command in the command prompt I’m still
> unable to use simpleRTK in python. I’m running the test code placed in the
> openRTK wiki installation page. I keep getting similar if not the same error
> that it is unable to find the _SimpleRTK module. It’s looking in the
> simpleRTK folder that gets installed into  I’m assuming this has to be the
> result of an incorrect installation but I can’t find anything online telling
> me what I did wrong. I’ve tried rebuilding with several different versions
> of swig (the default included version as well as the most up to date and
> several others) but keep coming back to the same error. Would you know how
> to fix this to get a proper installation or should I be trying on a
> different setup? Any help would be much appreciated.
>
>
>
> Thanks,
>
>
>
> -Daniel
>
>
> This e-mail may contain confidential and/or privileged information for the
> sole use of the intended recipient.
> Any review or distribution by anyone other than the person for whom it was
> originally intended is strictly prohibited.
> If you have received this e-mail in error, please contact the sender and
> delete all copies.
> Opinions, conclusions or other information contained in this e-mail may not
> be that of the organization.