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

can't build on windows / msys2 - mingw64 #2

Open
ah3nan opened this issue Dec 31, 2019 · 3 comments
Open

can't build on windows / msys2 - mingw64 #2

ah3nan opened this issue Dec 31, 2019 · 3 comments

Comments

@ah3nan
Copy link

ah3nan commented Dec 31, 2019

i can't build on windows / msys2 - mingw64 , it stops compiling at ffmpeg-dev-rs with no any errors or warning, It seems that build.rs script not working.

@colbyn
Copy link
Member

colbyn commented Jan 1, 2020

Ahh sorry for your trouble. Unfortunately I don’t have a windows license so I can’t test windows builds (at least for now, I'm very overloaded on other projects, but windows support is important to me since this is used in Imager).

Although I’m happy to accept PR requests. Otherwise, for now I’d recommend using another library, or running this in some linux environment.

@colbyn
Copy link
Member

colbyn commented Jan 1, 2020

Actually maybe this could run in Windows as is.

Also it’s very weird that cargo is not reporting any errors (I’m wondering if it’s from running cargo VIA some GUI tool or IDE that’s not showing it). If you can give me some error message that would help tremendously.

Besides the above, do you have make, sh, tar (with xz support) installed?

You can see how it's built from the build.rs file.

@AndreKR
Copy link

AndreKR commented Mar 18, 2020

It fails in build.rs:228:13 with "assertion failed: result.status.success()".

I'm using tar (GNU tar) 1.32 from MSYS2.

When I go to the directory and run

mkdir foo
tar -xJf archive\FFmpeg-FFmpeg-2722fc2.tar.xz -C foo
echo %errorlevel%

I works: errorlevel is 0 and the process takes a second or two, while the cargo build aborts almost immediately, so I think there is a difference here, maybe in out_path.

I tried to add additional println!s to build.rs and run cargo build again, but the output doesn't change. Is there a way I can modify and run build.rs? (I'm very new to Rust.)

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

No branches or pull requests

3 participants