Closed GoogleCodeExporter closed 8 years ago
Evgeny,
Looking at other IDA Pro 5.2 plugins, you may need to do the following in
addition to
patching the 5.2 SDK:
1. Use 'libvc.w64' from the IDA SDK, instead of 'libvc.w32'
2. Add ' /D "__EA64__" ' to the compilation options
3. Name the output file "python.p64"
If you want to use the build.py script, you can modify it to do these things by
changing the 'libvc' (line 298), adding a basemacro (line 221), and renaming the
plugin (lines 294 & 351).
You may also need to remove "WIN32" from the base macros, or replace it with
something else (I haven't tried).
Regards,
Dan
Original comment by doo...@gmail.com
on 18 Sep 2008 at 5:51
Hi,
One more thing you should do:
In swig/idaapi.i, lines 40-41, there are the constants BADADDR and BADSEL. You
should
change them from 0xFFFFFFFF to 0xFFFFFFFFFFFFFFFF, otherwise the functions in
idautils (such as CodeRefsTo) wouldn't work.
Regards,
Dan
Original comment by doo...@gmail.com
on 21 Sep 2008 at 11:49
I have managed to manually build a working plugin for 64-bit in the past.
There are a number of odds and ends that need to be checked but it should
not be a big deal
I will get back to 64-bit after 1.0 and make it a standard build for each
release.
Original comment by gergely.erdelyi
on 27 Sep 2008 at 1:54
Hi,
Me and Itai Shaham managed to build the plugin for 64 bit (windows).
We added build64.py script which makes the plugin (.p64) + /python64 directory
(that
should be copied to the IDA directory).
The patch file is attached (tested with swigwin-1.3.39, IDA SDK 5.4).
Ariel Shiftan
Original comment by shif...@gmail.com
on 5 May 2009 at 8:55
Attachments:
This bug is closed as the 64-bit build is now part of the regular binary
distributions.
Thanks to all who submitted ideas for this!
Original comment by gergely.erdelyi
on 21 Jul 2009 at 6:48
Original issue reported on code.google.com by
durkka@gmail.com
on 15 Sep 2008 at 1:33