Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding Windows Build Support #28

Closed
wants to merge 11 commits into from
Closed

Adding Windows Build Support #28

wants to merge 11 commits into from

Conversation

bannsec
Copy link

@bannsec bannsec commented Feb 6, 2016

Hey,

So I've made a few changes so that this will build and load in Windows. I've verified that it works in Python-64 installing into a virtualenv on my Windows 7x64 box. Couple things to note:

  • I changed the vex file to be vex.orig. I'm not sure what the vex file was used for, but in the Windows build it confuses it. If I'm reading the build python correctly, Linux/Mac should still build fine without that symlink, but I may be mis-understanding.
  • I had to make an assumption of a standard Cygwin64 build environment for Windows. MinGW wouldn't build 64-bit and MinGW-64 wouldn't build properly at all. Also, on the windows side the build will pull the cygwin1.dll file from \Cygwin64\bin.
  • Build still fails in general on Windows due to capstone, but I'm looking at the one separately. If the builder just removes the archinfo dependency, then it will build and the user can build the archinfo and capstone separately.
  • I included a link to my github repo for wheel files I'm making. Let me know how you would like to handle those things in the future. Windows is a pain to build for, so I'd expect the wheel files are going to be the preferred way to install.

Owlz and others added 11 commits February 5, 2016 22:08
Changed it to os.path.join instead of hard coding slash direction (for Windows compatibility)
Linking in my git repo where I am stashing Windows builds. Probably a better way to do this but for now it will at least let people get started in Windows.
Not sure what this file was for. When building in windows, it apparently doesn't handle the symbolic link correctly and fails out of the build. That said, I think it should still build fine in Linux without this file as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants