(no subject)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

(no subject)

juan carlos rebate
Hello, I am still engrossed in the previous topic of the screenshot,
if I got it to work thanks to your help but I do not get the optimal
quality results, this leads me to the conclusion that there is some
option not available in the compilation, so I I decided to compile it
from source, but as I said repeatedly, the verad documentation is
conspicuous by its absence.
Please, I do not need to recommend other projects, I do not need to
recommend other platforms or tools, I just need to know if they know
the correct way to compile it with the environment and configuration
that I am using.my entry is:

$ ./configure --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
--prefix=/usr/local --pkg-config=pkg-config
--pkg-config-flags=--static --extra-cflags=-static
--extra-ldflags=-static --enable-static --disable-shared --enable-gpl
--enable-avisynth --enable-libaom --enable-libfdk-aac
--enable-libfribidi --enable-libmp3lame --enable-libopus
--enable-libsoxr --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libx265

and the response of the configure script is as follows

libfdk_aac is incompatible with the gpl and --enable-nonfree is not specified.
how can I use both combinations? thanks
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate
my question is derived from the license problem that does not allow
gpl codecs together with non-free codecs
(I forgot to put subject, sorry forgive me)

El lun., 26 oct. 2020 a las 5:00, Juan carlos Rebate
(<[hidden email]>) escribió:

>
> Hello, I am still engrossed in the previous topic of the screenshot,
> if I got it to work thanks to your help but I do not get the optimal
> quality results, this leads me to the conclusion that there is some
> option not available in the compilation, so I I decided to compile it
> from source, but as I said repeatedly, the verad documentation is
> conspicuous by its absence.
> Please, I do not need to recommend other projects, I do not need to
> recommend other platforms or tools, I just need to know if they know
> the correct way to compile it with the environment and configuration
> that I am using.my entry is:
>
> $ ./configure --cross-prefix=x86_64-w64-mingw32- --arch=x86_64
> --prefix=/usr/local --pkg-config=pkg-config
> --pkg-config-flags=--static --extra-cflags=-static
> --extra-ldflags=-static --enable-static --disable-shared --enable-gpl
> --enable-avisynth --enable-libaom --enable-libfdk-aac
> --enable-libfribidi --enable-libmp3lame --enable-libopus
> --enable-libsoxr --enable-libvorbis --enable-libvpx --enable-libx264
> --enable-libx265
>
> and the response of the configure script is as follows
>
> libfdk_aac is incompatible with the gpl and --enable-nonfree is not specified.
> how can I use both combinations? thanks
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Zwanzig
On 10/25/2020 9:16 PM, Juan carlos Rebate wrote:
> my question is derived from the license problem that does not allow
> gpl codecs together with non-free codecs

I may be mistaken, but as I understand the GPL, if you're not distributing
anything (building for your own use), there are no license problems with
mixing GPL and non-free/encumbered/proprietary components. That means you
could use -enable-nonfree and -enable-gpl at the same time (I can't actually
try that at the moment).

If you -do- want to distribute ffmpeg, then you simply can't mix GPL and
proprietary/non-free parts.

z!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate
Yes, it's for personal use, However if you compile two separate versions
there would be no licensing issue if you share it, would it?

El lun., 26 oct. 2020 5:49, Carl Zwanzig <[hidden email]> escribió:

> On 10/25/2020 9:16 PM, Juan carlos Rebate wrote:
> > my question is derived from the license problem that does not allow
> > gpl codecs together with non-free codecs
>
> I may be mistaken, but as I understand the GPL, if you're not distributing
> anything (building for your own use), there are no license problems with
> mixing GPL and non-free/encumbered/proprietary components. That means you
> could use -enable-nonfree and -enable-gpl at the same time (I can't
> actually
> try that at the moment).
>
> If you -do- want to distribute ffmpeg, then you simply can't mix GPL and
> proprietary/non-free parts.
>
> z!
> _______________________________________________
> ffmpeg-user mailing list
> [hidden email]
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> [hidden email] with subject "unsubscribe".
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Zwanzig
On 10/25/2020 10:14 PM, Juan carlos Rebate wrote:
> However if you compile two separate versions
> there would be no licensing issue if you share it, would it?

If you "share" the build, then technically you're distributing it. The one
that's GPL only is perfectly fine to share (following the rules of the GPL,
please read them....), but if non-free parts are statically linked in, then
I don't think that one is distributable.

The questions that drive "can I distribute" include-
Is this a static or dynamic build?
Does it contain GPL components?
Does it contain non-free components?
There are cases where you can share a dynamic build (no GPL parts) that
links to non-free libraries but not a static build. (I think building with
BMD Decklink support is in that catagory.)

(Unfortunately, there doesn't seem to be a simple matrix to cover this.
Maybe I'll write one up sometime.)

A big question is whether you need --enable-gpl or not.


Please don't top-post on this list.

z!
Oh, ya, I Am Not A Lawyer
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate
It is not my intention to do top posting, this is because I do not like to use mail apps, I like the graphical interface web, and this does not have options to avoid it

De: Carl Zwanzig
Enviado: lunes, 26 de octubre de 2020 6:44
Para: [hidden email]
Asunto: Re: [FFmpeg-user] (no subject)

On 10/25/2020 10:14 PM, Juan carlos Rebate wrote:
> However if you compile two separate versions
> there would be no licensing issue if you share it, would it?

If you "share" the build, then technically you're distributing it. The one
that's GPL only is perfectly fine to share (following the rules of the GPL,
please read them....), but if non-free parts are statically linked in, then
I don't think that one is distributable.

The questions that drive "can I distribute" include-
Is this a static or dynamic build?
Does it contain GPL components?
Does it contain non-free components?
There are cases where you can share a dynamic build (no GPL parts) that
links to non-free libraries but not a static build. (I think building with
BMD Decklink support is in that catagory.)

(Unfortunately, there doesn't seem to be a simple matrix to cover this.
Maybe I'll write one up sometime.)

A big question is whether you need --enable-gpl or not.


Please don't top-post on this list.

z!
Oh, ya, I Am Not A Lawyer
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Zwanzig
On 10/26/2020 4:22 PM, juan carlos rebate wrote:
> It is not my intention to do top posting, this is because I do not like to use mail apps, I like the graphical interface web, and this does not have options to avoid it

Yes it does, I do that all the time, both in the android app and in a
browser (click on the three dots to expand the reply text, then edit).

z!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Reindl Harald
In reply to this post by juan carlos rebate


Am 27.10.20 um 00:22 schrieb juan carlos rebate:
> It is not my intention to do top posting, this is because I do not like to use mail apps, I like the graphical interface web, and this does not have options to avoid it

then learn to operate the graphical webinterface you like that much or
use a serious client

if it's too hard to compose a message properly what exactly do you like
so much - that are basics

i bet it also can do better than "(no subject)"
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate
In reply to this post by Carl Zwanzig


Enviado desde Correo para Windows 10

De: Carl Zwanzig
Enviado: martes, 27 de octubre de 2020 0:35
Para: [hidden email]
Asunto: Re: [FFmpeg-user] (no subject)

On 10/26/2020 4:22 PM, juan carlos rebate wrote:
> It is not my intention to do top posting, this is because I do not like to use mail apps, I like the graphical interface web, and this does not have options to avoid it

Yes it does, I do that all the time, both in the android app and in a
browser (click on the three dots to expand the reply text, then edit).

z!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Good afternoon, sorry that it took so long to update this thread, well I am still trying to use uar ffmpeg in my own way, but it seems that everything is going against me, now the problem is that if I try to compile in windows the process seems to be it carries out but then it doesn't actually do anything, it doesn't compile the executables or the dll, but in linux if you want to use the same set of commands, to compile I do the following:
I introduce it in the form of a column so that it does not occupy too much
./configure
--arch=x86_64
--target-os=mingw32
--cross-prefix=x86_64-w64-mingw32-
--prefix=/usr/local
--pkg-config=pkg-config
--pkg-config-flags=--static
--extra-cflags=-static
--extra-ldflags=-static
--extra-libs="-lm -lz -fopenmp"
--enable-static
--disable-shared
--enable-nonfree
--enable-gpl
--enable-avisynth
--enable-libaom
--enable-libfdk-aac
--enable-libfribidi
--enable-libmp3lame
--enable-libopus
--enable-libsoxr
--enable-libvorbis
--enable-libvpx
--enable-libx264
--enable-libx265
Make
If I compile it in linux in this way it compiles well, although along the way it tells me that some codecs are deprecated but it does compile, but this same set of commands in windows does not compile, if it indicates that it does but does not produce the final link, this it only happens to me with ffmpeg.
I have tried both with cygwin and with the monster developed by microsoft, (the wsl2)

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Eugen Hoyos-2
In reply to this post by Carl Zwanzig
Am Mo., 26. Okt. 2020 um 06:44 Uhr schrieb Carl Zwanzig <[hidden email]>:

>
> On 10/25/2020 10:14 PM, Juan carlos Rebate wrote:
> > However if you compile two separate versions
> > there would be no licensing issue if you share it, would it?
>
> If you "share" the build, then technically you're distributing it. The one
> that's GPL only is perfectly fine to share (following the rules of the GPL,
> please read them....), but if non-free parts are statically linked in, then
> I don't think that one is distributable.
>
> The questions that drive "can I distribute" include-
> Is this a static or dynamic build?

If the question is "am I allowed to distribute a binary based
on (L)GPL software" then the answer does not depend on
static or dynamic linking.

> Does it contain GPL components?
> Does it contain non-free components?

> There are cases where you can share a dynamic build (no GPL parts) that
> links to non-free libraries but not a static build. (I think building with
> BMD Decklink support is in that catagory.)

No.
Decklink is not GPL-compatible.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

kumowoon1025
In reply to this post by juan carlos rebate
Hi,

> Good afternoon, sorry that it took so long to update this thread, well I am still trying to use uar ffmpeg in my own way, but it seems that everything is going against me, now the problem is that if I try to compile in windows the process seems to be it carries out but then it doesn't actually do anything, it doesn't compile the executables or the dll, but in linux if you want to use the same set of commands, to compile I do the following:
> I introduce it in the form of a column so that it does not occupy too much
wut

> ./configure
> --arch=x86_64
> --target-os=mingw32
> --cross-prefix=x86_64-w64-mingw32-
> --prefix=/usr/local
> --pkg-config=pkg-config
> --pkg-config-flags=--static
> --extra-cflags=-static
> --extra-ldflags=-static
> --extra-libs="-lm -lz -fopenmp"
> --enable-static
> --disable-shared
> --enable-nonfree
> --enable-gpl
> --enable-avisynth
> --enable-libaom
> --enable-libfdk-aac
> --enable-libfribidi
> --enable-libmp3lame
> --enable-libopus
> --enable-libsoxr
> --enable-libvorbis
> --enable-libvpx
> --enable-libx264
> --enable-libx265
> Make
> If I compile it in linux in this way it compiles well, although along the way it tells me that some codecs are deprecated but it does compile, but this same set of commands in windows does not compile, if it indicates that it does but does not produce the final link, this it only happens to me with ffmpeg.
Does that automatically cross-compile with just make? I thought you would need to add --enable-cross-compile. Also I’d have thought you’d want a different prefix at the least for cross-compiling on linux and compiling on windows.
> I have tried both with cygwin and with the monster developed by microsoft, (the wsl2)

On wsl2, you’d just compile as if you were on a linux system, and not bother with mingw32, it’s basically a vm isnt it?

Regards,
Ted Park

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Eugen Hoyos-2
In reply to this post by juan carlos rebate
Am So., 1. Nov. 2020 um 19:49 Uhr schrieb juan carlos rebate
<[hidden email]>:

> Good afternoon, sorry that it took so long to update this thread, well I am still trying
> to use uar ffmpeg in my own way, but it seems that everything is going against me,
> now the problem is that if I try to compile in windows the process seems to be it
> carries out but then it doesn't actually do anything, it doesn't compile the
> executables or the dll, but in linux if you want to use the same set of commands,
> to compile I do the following:
> I introduce it in the form of a column so that it does not occupy too much
> ./configure
> --arch=x86_64
> --target-os=mingw32
> --cross-prefix=x86_64-w64-mingw32-
> --prefix=/usr/local
> --pkg-config=pkg-config
> --pkg-config-flags=--static

> --extra-cflags=-static

Is this a useful option?

> --extra-ldflags=-static

(This option sometimes causes issues and I believe it should not
be necessary on Windows)

> --extra-libs="-lm -lz -fopenmp"

Why is this necessary?
Is there a bug we don't know about?
(Or just a bug in an external library?)

> --enable-static
> --disable-shared

These are unneeded.

> --enable-nonfree
> --enable-gpl
> --enable-avisynth
> --enable-libaom
> --enable-libfdk-aac
> --enable-libfribidi
> --enable-libmp3lame
> --enable-libopus
> --enable-libsoxr
> --enable-libvorbis
> --enable-libvpx
> --enable-libx264
> --enable-libx265

> Make

(I suspect there is no operating system with a command "Make")

> If I compile it in linux in this way it compiles well, although along the way it
> tells me that some codecs are deprecated but it does compile, but this
> same set of commands in windows does not compile, if it indicates that it
> does but does not produce the final link, this it only happens to me with ffmpeg.

Very generally, I would not expect the same non-trivial configure line
to work on
Linux and Windows (think of cross- vs native compilation).

> I have tried both with cygwin and with the monster developed by microsoft,

> (the wsl2)

In my tests, I saw some issues with wsl2, I recommend wsl (1)
for FFmpeg Windows compilation.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Eugen Hoyos-2
In reply to this post by kumowoon1025
Am So., 1. Nov. 2020 um 21:14 Uhr schrieb Edward Park <[hidden email]>:

> > ./configure
> > --arch=x86_64
> > --target-os=mingw32
> > --cross-prefix=x86_64-w64-mingw32-

> Does that automatically cross-compile with just make?
> I thought you would need to add --enable-cross-compile.

No, --cross-prefix is enough.

[...]

> > I have tried both with cygwin and with the monster developed by microsoft, (the wsl2)
>
> On wsl2, you’d just compile as if you were on a linux system, and not bother with mingw32, it’s basically a vm isnt it?

wsl2 compilation has not worked for me, there is a line length limitation afair.
ymmv

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate
In reply to this post by Carl Eugen Hoyos-2


Enviado desde Correo para Windows 10

De: Carl Eugen Hoyos
Enviado: domingo, 1 de noviembre de 2020 21:14
Para: FFmpeg user questions
Asunto: Re: [FFmpeg-user] (no subject)

Am So., 1. Nov. 2020 um 19:49 Uhr schrieb juan carlos rebate
<[hidden email]>:

> Good afternoon, sorry that it took so long to update this thread, well I am still trying
> to use uar ffmpeg in my own way, but it seems that everything is going against me,
> now the problem is that if I try to compile in windows the process seems to be it
> carries out but then it doesn't actually do anything, it doesn't compile the
> executables or the dll, but in linux if you want to use the same set of commands,
> to compile I do the following:
> I introduce it in the form of a column so that it does not occupy too much
> ./configure
> --arch=x86_64
> --target-os=mingw32
> --cross-prefix=x86_64-w64-mingw32-
> --prefix=/usr/local
> --pkg-config=pkg-config
> --pkg-config-flags=--static

> --extra-cflags=-static

Is this a useful option?

> --extra-ldflags=-static

(This option sometimes causes issues and I believe it should not
be necessary on Windows)

> --extra-libs="-lm -lz -fopenmp"

Why is this necessary?
Is there a bug we don't know about?
(Or just a bug in an external library?)

> --enable-static
> --disable-shared

These are unneeded.

> --enable-nonfree
> --enable-gpl
> --enable-avisynth
> --enable-libaom
> --enable-libfdk-aac
> --enable-libfribidi
> --enable-libmp3lame
> --enable-libopus
> --enable-libsoxr
> --enable-libvorbis
> --enable-libvpx
> --enable-libx264
> --enable-libx265

> Make

(I suspect there is no operating system with a command "Make")

> If I compile it in linux in this way it compiles well, although along the way it
> tells me that some codecs are deprecated but it does compile, but this
> same set of commands in windows does not compile, if it indicates that it
> does but does not produce the final link, this it only happens to me with ffmpeg.

Very generally, I would not expect the same non-trivial configure line
to work on
Linux and Windows (think of cross- vs native compilation).

> I have tried both with cygwin and with the monster developed by microsoft,

> (the wsl2)

In my tests, I saw some issues with wsl2, I recommend wsl (1)
for FFmpeg Windows compilation.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Actually my way of compiling is simpler but as it did not work in windows I looked in google for some way to do it and I came up with a tutorial, my way that I have been using since ffmpeg 2.4.4 is this;
./configure --enable-gpl --enable-nonfree --enable-encoders --enable-decoders --enable-muxers --enable-demuxers.
In linux in this way it compiles me perfect except that it does not link me statically but dynamically for that reason the static, but in windows with my way it tells me that the compiler tests failed, with wsl1 it gave me more errors than with wsl2
The tutorial is https://superuser.com/questions/1425350/how-to-compile-the-best-version-of-ffmpeg-for-windows
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Eugen Hoyos-2
Am So., 1. Nov. 2020 um 21:41 Uhr schrieb juan carlos rebate
<[hidden email]>:

> Actually my way of compiling is simpler but as it did not work in windows I looked
> in google for some way to do it and I came up with a tutorial, my way that I have
> been using since ffmpeg 2.4.4 is this;
> ./configure --enable-gpl --enable-nonfree --enable-encoders --enable-decoders --enable-muxers --enable-demuxers.

The following options have no effect:
--enable-nonfree --enable-encoders --enable-decoders --enable-muxers
--enable-demuxers

> In linux in this way it compiles me perfect except that it does not link me statically
> but dynamically for that reason the static,

On Windows, you normally don't care about a dynamic compile as no incompatible
C library should exist.

> but in windows with my way it tells me that the compiler tests failed

Which compiler did you install?
With wsl, you can use msvc, (Microsoft) clang and - with a little additional
effort - gcc.

Please cut your quotes, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

juan carlos rebate


Enviado desde Correo para Windows 10

De: Carl Eugen Hoyos
Enviado: domingo, 1 de noviembre de 2020 23:27
Para: FFmpeg user questions
Asunto: Re: [FFmpeg-user] (no subject)

Am So., 1. Nov. 2020 um 21:41 Uhr schrieb juan carlos rebate
<[hidden email]>:

> Actually my way of compiling is simpler but as it did not work in windows I looked
> in google for some way to do it and I came up with a tutorial, my way that I have
> been using since ffmpeg 2.4.4 is this;
> ./configure --enable-gpl --enable-nonfree --enable-encoders --enable-decoders --enable-muxers --enable-demuxers.

The following options have no effect:
--enable-nonfree --enable-encoders --enable-decoders --enable-muxers
--enable-demuxers

> In linux in this way it compiles me perfect except that it does not link me statically
> but dynamically for that reason the static,

On Windows, you normally don't care about a dynamic compile as no incompatible
C library should exist.

> but in windows with my way it tells me that the compiler tests failed

Which compiler did you install?
With wsl, you can use msvc, (Microsoft) clang and - with a little additional
effort - gcc.

Please cut your quotes, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
The options that I indicate are listed in the configure file, if it does not make sense for what is included ?, what would be the correct combination that includes free and non-free tools if the options of the configure file do not make sense?
en este momento estoy usando cygwin con mingw, wsl no puedo utilizarlo porque es un absoluto engendro disfuncional
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Carl Eugen Hoyos-2
Am Mo., 2. Nov. 2020 um 00:09 Uhr schrieb juan carlos rebate
<[hidden email]>:

> The options that I indicate are listed in the configure file,

No.

> if it does not make sense for what is included ?

Most of the options never make sense.

> what would be the correct combination that includes free and non-free
> tools if the options of the configure file do not make sense?

You did not include any non-free optional parts, you therefore don't
need --enable-nonfree.

I can only repeat:
If you cannot use prebuilt binaries but have to build Windows binaries
yourself, wsl is the best option.

If you need more help, please fix your mailer and your quoting, Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Building on windows

Carl Zwanzig
On 11/1/2020 3:33 PM, Carl Eugen Hoyos wrote:
> If you cannot use prebuilt binaries but have to build Windows binaries
> yourself, wsl is the best option.

Are there specific technical reasons for that? I've been using MinGW-64 and
that works rather well (for me), next would be VC++ since I occasionally
need to build using it, WSL I'd have to install.

z!
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: (no subject)

Reindl Harald
In reply to this post by juan carlos rebate


Am 02.11.20 um 00:09 schrieb juan carlos rebate:
> On Windows, you normally don't care about a dynamic compile as no incompatible
> C library should exist

in which perfect world?

other than on proper operating systems with package managers and
dependencies you even can end in one installer overwrites existing
libraries with incompatible versions
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Building on windows

Carl Eugen Hoyos-2
In reply to this post by Carl Zwanzig
Am Mo., 2. Nov. 2020 um 00:43 Uhr schrieb Carl Zwanzig <[hidden email]>:
>
> On 11/1/2020 3:33 PM, Carl Eugen Hoyos wrote:
> > If you cannot use prebuilt binaries but have to build Windows binaries
> > yourself, wsl is the best option.
>
> Are there specific technical reasons for that? I've been using MinGW-64
> and that works rather well (for me), next would be VC++ since I
> occasionally need to build using it, WSL I'd have to install.

I haven't used msys for a very long time (you can use both mingw and
vc++ with wsl), I consider wsl a simple solution.

Carl Eugen
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
12