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

Native Windows build #71

Open
mkeeter opened this issue Jun 5, 2015 · 24 comments
Open

Native Windows build #71

mkeeter opened this issue Jun 5, 2015 · 24 comments

Comments

@mkeeter
Copy link
Owner

mkeeter commented Jun 5, 2015

I've started working on a native Windows build in this branch
(instructions emerging here).

Current blockers:

  • libpng is being built without any symbols,
  • We're missing a few important symbols from python3.dll
    Both of these are causing the linker to fail.

@s7726, have you gotten any farther with a native build?

@s7726
Copy link

s7726 commented Jun 8, 2015

I have not been able to get to this no.

On Fri, Jun 5, 2015, 4:38 PM Matt Keeter notifications@github.com wrote:

I've started working on a native Windows build in this branch
https://github.com/mkeeter/antimony/tree/feature/win32-build
(instructions emerging here
https://github.com/mkeeter/antimony/blob/feature/win32-build/BUILDING.md#windows
).

Current blockers:

  • libpng is being built without any symbols,
  • We're missing a few important symbols from python3.dll Both of these
    are causing the linker to fail.

@s7726 https://github.com/s7726, have you gotten any farther with a
native build?


Reply to this email directly or view it on GitHub
#71.

@carlosjln
Copy link

I wish this build comes soon, i tried building one on xubuntu and it failed (i'm a windows user)

@Betosaurus
Copy link

I am interested in a Windows build too.

@DeadlyDad
Copy link

Any news on a Windows binary? I'm using the v0.8.0 on a Xubuntu virtual machine, but that's a little sketchy.

@DeadlyDad
Copy link

I am absolutely flat broke, but if someone either has or wants to make some money.....

@mkeeter
Copy link
Owner Author

mkeeter commented Oct 14, 2015

No news on Windows binaries. I've had a few pings from people interested, but no solid followup yet.

Any reason why you're still on 0.8.0? That's a pretty old release...

@DeadlyDad
Copy link

  1. ...which is why the bounty link. Those who want it and have a few bucks to spare provide the financial incentive for someone to take the time to make it happen.
  2. I followed the compiling instructions that people put up in a VM Xubuntu environment, but could never get it to work, and, as I haven't done any real coding in years, couldn't figure out why it wouldn't. The only reason that I have been able to use Antimony is that someone posted a 0.8.0 .deb file. (Even that needed the compiling prerequisites to actually install it.) If someone would put together a .deb of the current release, that would be GREAT. BTW, is it possible to export a Collada or .obj file yet?

@TLC123
Copy link

TLC123 commented Mar 3, 2016

I seeded an tiny bounty on Bountysource. Anyone else up for a buck or two?

@DeadlyDad
Copy link

Anybody willing to have mercy on us poor Windows shlubs? Some of just don't have the time to learn a complete coding environment to compile a single program.

@mkeeter
Copy link
Owner Author

mkeeter commented Jan 18, 2017

I had my annual fight against Windows; unlike in past years, I came out victorious:

screen shot 2017-01-17 at 9 02 11 pm

Everything is merged into the develop branch, with instructions here. Building is a fairly hands-on process, but those instructions should be clear.

Building an installer is a whole different can of worms, and something I'll punt on for now.

@DeadlyDad – want to try following those instructions and see if you can get something running?

@carlosjln
Copy link

Awesome! I'll give it a try sometime soon :)

@DeadlyDad
Copy link

DeadlyDad commented Jan 22, 2017 via email

mkeeter added a commit that referenced this issue Jan 22, 2017
@mkeeter
Copy link
Owner Author

mkeeter commented Jan 22, 2017

  1. Instructions say '/mingw64/home/$USERNAME'. Should be '\msys64\home$USERNAME'?

Okay, clarified in 8fd10a9

  1. Couldn't compile Boost. Help!

I'm not totally sure what's going on here, but it looks like you're in the wrong MSYS shell. You should be opening the "MSYS2 MinGW 64-bit" shell application, which has a prompt containing MINGW64:

  • My prompt is mkeeter@MATTHEWKEETF381 MINGW64 ~/boost_1_63_0
  • Yours is spamt@DESKTOP-D1M1OJ0 MSYS ~/boost_1_63_0

Can you try opening the correct shell and walking through the directions again?

@DeadlyDad
Copy link

DeadlyDad commented Jan 23, 2017 via email

mkeeter added a commit that referenced this issue Jan 24, 2017
Relevant to [this comment](#71 (comment))
@mkeeter
Copy link
Owner Author

mkeeter commented Jan 24, 2017

Okay, I think the issue is the path to cmake. Can you try invoking it as
BOOST_ROOT=~/boost_1_63_0/ BOOST_LIBRARYDIR=~/boost_1_63_0/stage/ /mingw64/bin/cmake -G"MSYS Makefiles" ..
instead?

Updated the docs in commit 48fdfc6

@DeadlyDad
Copy link

DeadlyDad commented Jan 25, 2017 via email

@DeadlyDad
Copy link

DeadlyDad commented Jan 25, 2017 via email

@mkeeter
Copy link
Owner Author

mkeeter commented Jan 31, 2017

Okay, how about running pacman -Q in a MSYS MinGW64 shell to list installed packages?

When I do so, I get this list. Can you diff that with your results and see what's missing?

@DeadlyDad
Copy link

DeadlyDad commented Feb 3, 2017 via email

@mkeeter
Copy link
Owner Author

mkeeter commented Feb 4, 2017

I think the important one that you're missing is make – can you install it (pacman -S make) and see if cmake becomes happy?

@eltercerlugar
Copy link

Hi all. Im a Windows 10 user, with a enough clean system installation. I follow the instructions to build the Windows enviroment to work with Antimony, and after follow all the steps i could not compile the Antimony package.

The problem seemed to be the Boost package, so i found a package that, added to the list of packaged installed with pacman, make my antimony runs in windows.

I added this command:

Pacman -S base-devel

before the "clone and build antimony" part, and i could finally avoid the error after prompt "BOOST_ROOT=/boost_1_63_0/ BOOST_LIBRARYDIR=/boost_1_63_0/stage/ /mingw64/bin/cmake -G"MSYS Makefiles" .."

Hope this helps anyone.

@seantapscott
Copy link

I got the same cmake configuration errors as DeadlyDad on the cmake step, and had to run
pacman -s make as well. Not entirely successful yet, but still working on it. Really excited, thank you mkeeter.

@seantapscott
Copy link

And its working. Not entirely sure what to do next, but boom!

@roboter
Copy link

roboter commented Sep 4, 2018

@seantapscott could you write instruction how to build, on clean PC,
with all versions.
I have tried many times and failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants