anybody want to continue media-autobuild_suite?

Any other question that don't fit into the other support categorizes.
jbalvarado
Posts: 50
Joined: Thu Oct 03, 2013 3:47 pm

anybody want to continue media-autobuild_suite?

Post by jbalvarado » Mon Aug 11, 2014 7:03 pm

Hello everybody,
I was writing the build script https://github.com/jb-alvarado/media-autobuild_suite , with them people are able to compile ffmpeg and other tools under windows with msys2 for 32 and 64 bit.

The project is now to big for me, because I have no time anymore to support it.

Is here anybody interested to continue this project?

Regards

jb_

svnpenn
Posts: 263
Joined: Tue Nov 01, 2011 12:19 am

Re: anybody want to continue media-autobuild_suite?

Post by svnpenn » Tue Aug 12, 2014 3:30 am

Well if you are just going to delete it, I can take it over for the time being.

If it means anything, I am top 10 all time FFmpeg on Stack Overflow

http://stackoverflow.com/tags/ffmpeg/topusers

jbalvarado
Posts: 50
Joined: Thu Oct 03, 2013 3:47 pm

Re: anybody want to continue media-autobuild_suite?

Post by jbalvarado » Tue Aug 12, 2014 11:58 am

Hello svnpenn,
tank you for your offer! It want be nice when you continue the project! You are also able to fix problems, when they come? At the moment the script works fine, but some times code change from the packets and then maybe it need a little work. kvazaar is one of this problem kids, because of is beta status.

When you have any questions about the code, I will help and explain. In the wiki I have also some explanations, maybe not the best for reading because of my English skills, but here is a little overview.

github have the option that I can transfer the project, so when you want I can do this to you.

Regards!

jb_

svnpenn
Posts: 263
Joined: Tue Nov 01, 2011 12:19 am

Re: anybody want to continue media-autobuild_suite?

Post by svnpenn » Tue Aug 12, 2014 2:10 pm

Right now my focus is on getting a feature complete Linux environment on Windows. I am having issues with both Cygwin and MSYS2. Hopefully this will be resolved this month, until then I will probably not be able to work on FFmpeg.

If that is acceptable then I can take over now.

User avatar
Zeranoe
Site Admin
Posts: 703
Joined: Sat May 07, 2011 7:12 pm
Contact:

Re: anybody want to continue media-autobuild_suite?

Post by Zeranoe » Tue Aug 12, 2014 4:12 pm

svnpenn wrote:Right now my focus is on getting a feature complete Linux environment on Windows. I am having issues with both Cygwin and MSYS2.
There are so many ways to compile FFmpeg. The best I've found to be is cross compiling, the worst is MSVC. Somewhere between there is Cygwin and MSYS. I think Cygwin beats out MSYS for many reasons, but it still doesn't compete with cross compiling.

svnpenn
Posts: 263
Joined: Tue Nov 01, 2011 12:19 am

Re: anybody want to continue media-autobuild_suite?

Post by svnpenn » Tue Aug 12, 2014 4:18 pm

Zeranoe wrote: There are so many ways to compile FFmpeg. The best I've found to be is cross
compiling, the worst is MSVC. Somewhere between there is Cygwin and MSYS. I
think Cygwin beats out MSYS for many reasons, but it still doesn't compete with
cross compiling.
I agree with this completely. However, with all due respect, I do not want to
take "the easy way out". I want to help fix the issues with Cygwin and MSYS2,
and also improve my Windows build script for FFmpeg. In this way, I can help
future Windows users who want to get into developing.

jbalvarado
Posts: 50
Joined: Thu Oct 03, 2013 3:47 pm

Re: anybody want to continue media-autobuild_suite?

Post by jbalvarado » Tue Aug 12, 2014 4:49 pm

I don't know cygwin, but I know that msys2 is much better then msys1. And with pacman you have also a nice packet manager, not so a big one like apt-get but it is enough. You found also now many tools and libs: https://github.com/Alexpux/MINGW-packages

The good thing on cross compile on linux is, it is faster, I think when it is possible to cross compile on mac it is even faster. But beside of that msys2 makes a great job.

What you miss at the moment in msys?

I think it is ok to let the project a bit there until you have more time. Or somebody else want help to.

Regards

jb_

svnpenn
Posts: 263
Joined: Tue Nov 01, 2011 12:19 am

Re: anybody want to continue media-autobuild_suite?

Post by svnpenn » Tue Aug 12, 2014 5:06 pm

jbalvarado wrote: What you miss at the moment in msys?
MSYS2 and in turn MinGW chmod has been crippled for years

http://sourceforge.net/p/mingw/bugs/1475

http://sourceforge.net/p/msys2/tickets/60

It is likely to not be fixed. The workaround is to use a Shebang with Bash
scripts. While this is good practice anyway, it should not be required by the
operating system. I also have an open bounty on that

stackoverflow.com/q/25165808/should-i-use-a-shebang-with-bash-scripts

jbalvarado
Posts: 50
Joined: Thu Oct 03, 2013 3:47 pm

Re: anybody want to continue media-autobuild_suite?

Post by jbalvarado » Tue Aug 12, 2014 6:00 pm

Ah, I never has use this things :). Before I always call the sh script from batch with:

mintty.exe /bin/sh -l script.sh

Now I try it in the way what you have on stackoverflow, with: #!/bin/sh -l on top off the script.sh file and call it from batch with:

mintty.exe script.sh

I also use a shortcut to mintty.exe with: *\msys64\usr\bin\mintty.exe /bin/sh -l for general use.

And that also work. But I really have not so much knowledge about chmod things. In windows I don't use the acp and my msys2 runs also not on c:\.

qyot27
Posts: 84
Joined: Wed Jan 23, 2013 4:10 pm
Contact:

Re: anybody want to continue media-autobuild_suite?

Post by qyot27 » Wed Aug 13, 2014 2:38 pm

It doesn't require one here:

The contents of audio.sh:

Code: Select all

mediainfo opus-tools-build.txt
date

Code: Select all

$ ls -l audio.sh
-rw-r--r-- 1 Stephen None 36 Aug 13 08:07 audio.sh

Code: Select all

$ ./audio.sh
General
Complete name                            : opus-tools-build.txt
File size                                : 2.41 KiB


Wed, Aug 13, 2014  8:07:26 AM
No #! line and it still executes. The only point is that tab auto-completion doesn't pick it up if the #! line isn't present. But it doesn't stop it from executing in that case.

If I add the #!,

Code: Select all

$ ls -l audio.sh
-rwxr-xr-x 1 Stephen None 54 Aug 13 09:09 audio.sh
For ls to see the ACLs and translate them to POSIX permissions, you have to mount the drive with the 'acl' option*. This is as true for Cygwin as it is for MSys2. The difference is that Cygwin has 'acl' on by default, whereas MSys2 uses 'noacl' by default and therefore shows you only what can be approximated (go into /etc/fstab and change it to 'acl' and the output will change the next time you launch MSys2).

*https://www.cygwin.com/cygwin-ug-net/using.html:

Code: Select all

  acl       - Cygwin uses the filesystem's access control lists (ACLs) to
              implement real POSIX permissions (default).  This flag only
	      affects filesystems supporting ACLs (NTFS, for instance) and
	      is ignored otherwise.

  noacl     - Cygwin ignores filesystem ACLs and only fakes a subset of
	      permission bits based on the DOS readonly attribute.  This
	      behaviour is the default on FAT and FAT32.  The flag is
	      ignored on NFS filesystems.
But even with acl on, the behavior in regard to displaying the permission changes from chmod is a bit wonky. Sometimes it shows, sometimes it doesn't. All [probably] because there's a very intricate set of underlying environment variables and filesystem-related behavior going on that exert their will on the issue - relative paths may/may not show the changes, absolute paths very probably do. If PATHEXT and PATH are set just right this one way, it might let ls show you an x bit on a hashbang-less script, or it might not. When I was testing it, it was all over the map and I couldn't pin it to a singular golden configuration.

Not that I think it matters too much, since there's only a couple of cases that it might affect (source packaging for cross-platform development and dealing with pushing up to a VCS), and casual users wanting to compile things would never run into those. Developers that have to deal with those things would already know Windows is not exactly suitable for that when the target is *nix and Windows, or they use the tools provided by their VCS to override the problem and make sure the files are committed with the right permissions (Git provides this with the --chmod option). For general user-written scripts that aren't meant for development, the only thing that happens is the inconvenience of not having tab auto-completion if the #! isn't there.

From the MinGW mailing list back in 2010:

Code: Select all

From: Charles Wilson <[email protected]>
Subject: Re: chmod broken?
Newsgroups: gmane.comp.gnu.mingw.msys
Date: 2010-03-05 05:26:25 GMT (4 years, 23 weeks, 8 hours and 48 minutes ago)

Chris Sutcliffe wrote:
>> It seems MSYS uses by default the equivalent of Cygwin's "noacl" mount
>> option:
>>
>> * The Access Control List of the file is ignored.
>> * The read flag is always on.
>> * The DOS read-only attribute controls the user write flag.
>> * Files are considered to be executable if the filename ends with .bat,
>> .com or .exe, or if its content starts with #!.
>> * Directories have the execute flags always on.
> 
> Hrm... good to know, thank you.
> 
> Is it possible to override the noacl mount option?

As far as I'm aware, this is considered a /feature/, not a bug. MSYS
deliberately ignores all those posixism, so that the windows access
rules control things. (E.g. the unix permission "bits" are little white
lies. Even if 'ls' says -rwxrwxrwx, if the Windows Security settings say
"no" then you can't.

But...MSYS is aimed mostly at the windows user, who is (arguably)
familiar with setting permissions on files via the windows Security
tools, but...'chmod? huh?'

--
Chuck

Post Reply
'