From: Georgi P. <gog...@gm...> - 2011-01-28 14:49:39
|
Hi, I had a conversation with JonY yesterday and he invited me to will help you to create better working and tested EVR (Enhanced Video Renderer) evr.h header file. As I look at the Windows SDK headers, I will provide description (without actual code or declarations) of the internal structure and will test the header. He or somebody else will then read my description and improve the header inside mingw-w64. As I am implementing EVR support in MPlayer, only the mingw32-w64 project has evr.h as a starting point and I will use it (test it as well) while my development is progressing. What is the next step? Greetings, Georgi |
From: JonY <jo...@us...> - 2011-01-28 15:24:48
Attachments:
0xED74C077.asc
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/28/2011 22:49, Georgi Petrov wrote: > Hi, > > I had a conversation with JonY yesterday and he invited me to will > help you to create better working and tested EVR (Enhanced Video > Renderer) evr.h header file. As I look at the Windows SDK headers, I > will provide description (without actual code or declarations) of the > internal structure and will test the header. He or somebody else will > then read my description and improve the header inside mingw-w64. > > As I am implementing EVR support in MPlayer, only the mingw32-w64 > project has evr.h as a starting point and I will use it (test it as > well) while my development is progressing. > > What is the next step? > > Greetings, > Georgi > Hi and Welcome to mingw-w64. The first step would be to check and verify the existing interface layouts found in mingw-w64 evr.h for errors. You should be able to describe them by member layout order and input/output parameter type. It'll be a long process. For convenience of searching, you can post each interface as a separate mail to the public list, with subjects like "IMFVideoPresenter Interface" or "IMFDesiredSample Interface". Maybe we should open up a mingw-w64-documentation list for you to post them. :) There are also other EVR related headers like opmapi.h and ever9.h. If possible, I would like you to check them. You can grab the latest headers code via svn: svn co https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/trunk/mingw-w64-headers/include/ This will give you the latest copy of the psdk headers. Well, that is all for now, no need to rush. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) iEYEARECAAYFAk1C2zUACgkQp56AKe10wHfjHQCfTAEzKEdf668lEGhsHdcSAg6V J+UAnRfBdJcAPQjzaw72EiQJ3BgXc4h7 =NIv7 -----END PGP SIGNATURE----- |
From: JonY <jo...@us...> - 2011-01-28 16:15:25
Attachments:
0xED74C077.asc
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/28/2011 23:05, JonY wrote: > On 1/28/2011 22:49, Georgi Petrov wrote: >> Hi, > >> I had a conversation with JonY yesterday and he invited me to will >> help you to create better working and tested EVR (Enhanced Video >> Renderer) evr.h header file. As I look at the Windows SDK headers, I >> will provide description (without actual code or declarations) of the >> internal structure and will test the header. He or somebody else will >> then read my description and improve the header inside mingw-w64. > >> As I am implementing EVR support in MPlayer, only the mingw32-w64 >> project has evr.h as a starting point and I will use it (test it as >> well) while my development is progressing. > >> What is the next step? > >> Greetings, >> Georgi > > > Hi and Welcome to mingw-w64. > > The first step would be to check and verify the existing interface > layouts found in mingw-w64 evr.h for errors. > > You should be able to describe them by member layout order and > input/output parameter type. It'll be a long process. For convenience of > searching, you can post each interface as a separate mail to the public > list, with subjects like "IMFVideoPresenter Interface" or > "IMFDesiredSample Interface". > > Maybe we should open up a mingw-w64-documentation list for you to post > them. :) > > There are also other EVR related headers like opmapi.h and ever9.h. If > possible, I would like you to check them. > > You can grab the latest headers code via svn: > > svn co > https://mingw-w64.svn.sourceforge.net/svnroot/mingw-w64/trunk/mingw-w64-headers/include/ > > This will give you the latest copy of the psdk headers. > > Well, that is all for now, no need to rush. > Looks like mingw-w64-documentation list is up and and running. We've setup a list for documentation to be sent in. So please subscribe via <https://lists.sourceforge.net/lists/listinfo/mingw-w64-documentation> and post documentation there. Thanks. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) iEYEARECAAYFAk1C5xIACgkQp56AKe10wHfLSQCfVBRILB//pLZqG8FsCsWrgl9x FzUAn2mlgFymvc9bvMsb5isGgAlx7JOx =auiE -----END PGP SIGNATURE----- |
From: Dongsheng S. <don...@gm...> - 2011-01-30 02:39:30
|
Hi JonY, In r4001, you add 'misc/mbwc.c' to mingw-w64-crt/Makefile.am, but I can not find mbwc.c, only found misc/mingw_mbwc_convert.c. |
From: JonY <jo...@us...> - 2011-01-30 10:54:08
Attachments:
0xED74C077.asc
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/30/2011 10:39, Dongsheng Song wrote: > Hi JonY, > > In r4001, you add 'misc/mbwc.c' to mingw-w64-crt/Makefile.am, but I can not > find mbwc.c, only > found misc/mingw_mbwc_convert.c. > Thanks. Trunk is now fixed. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) iEYEARECAAYFAk1FQz8ACgkQp56AKe10wHcYYACfY/ooYRxtCH5Hyh5ycx+sqYjw qigAn25wC/qtxonKbfbtfefZiEoCw3gW =vsbP -----END PGP SIGNATURE----- |
From: Georgi P. <gog...@gm...> - 2011-02-01 19:36:07
|
Hello, As I understand, all mingw-w64 files are under ZPL license. Then why evr.h starts with: /** * This file has no copyright assigned and is placed in the Public Domain. * This file is part of the w64 mingw-runtime package. * No warranty is given; refer to the file DISCLAIMER.PD within this package. */ When this is sorted out, I will start describing the interfaces in mingw-w64 documentation mailing list. Also - I can't find information about which parts of mingw-w64 are under which license. I hope you are using ZPL version 2.0, because it is GPL compatible. |
From: Georgi P. <gog...@gm...> - 2011-02-01 19:38:19
|
If headers are in public domain, I will be able to include evr.h in mingw later, but if the headers are ZPL licensed, I wouldn't. The problem is that mingw's headers are in the public domain. Is there any chance that the headers from mingw-w64 are also in public domain (as is written in the beginning of the current evr.h)? |
From: Kai T. <kti...@go...> - 2011-02-01 19:44:15
|
2011/2/1 Georgi Petrov <gog...@gm...>: > If headers are in public domain, I will be able to include evr.h in > mingw later, but if the headers are ZPL licensed, I wouldn't. > > The problem is that mingw's headers are in the public domain. Is there > any chance that the headers from mingw-w64 are also in public domain > (as is written in the beginning of the current evr.h)? We place headers (not source) into PD. But not in all legislatives there is the term Public Domain usable. Therefore we introduced for such cases the fallback ZPL license as it fits most the intention of somebody contributing to mingw-w64. Regards, Kai |
From: Georgi P. <gog...@gm...> - 2011-02-01 20:41:22
|
On Tue, Feb 1, 2011 at 9:44 PM, Kai Tietz <kti...@go...> wrote: > 2011/2/1 Georgi Petrov <gog...@gm...>: >> If headers are in public domain, I will be able to include evr.h in >> mingw later, but if the headers are ZPL licensed, I wouldn't. >> >> The problem is that mingw's headers are in the public domain. Is there >> any chance that the headers from mingw-w64 are also in public domain >> (as is written in the beginning of the current evr.h)? > > We place headers (not source) into PD. But not in all legislatives > there is the term Public Domain usable. Therefore we introduced for > such cases the fallback ZPL license as it fits most the intention of > somebody contributing to mingw-w64. > > Regards, > Kai Ok, I understand. So currently evr.h is in the public domain, but when I start helping improving it, you will transfer it to ZPL? Is there an option that evr.h remains in PD while I'm helping, so that later it could be included in mingw headers? My point is that building MPlayer (which uses mingw) will be *much* easier that way. What do you think? |
From: Kai T. <kti...@go...> - 2011-02-01 20:47:39
|
2011/2/1 Georgi Petrov <gog...@gm...>: > On Tue, Feb 1, 2011 at 9:44 PM, Kai Tietz <kti...@go...> wrote: >> 2011/2/1 Georgi Petrov <gog...@gm...>: >>> If headers are in public domain, I will be able to include evr.h in >>> mingw later, but if the headers are ZPL licensed, I wouldn't. >>> >>> The problem is that mingw's headers are in the public domain. Is there >>> any chance that the headers from mingw-w64 are also in public domain >>> (as is written in the beginning of the current evr.h)? >> >> We place headers (not source) into PD. But not in all legislatives >> there is the term Public Domain usable. Therefore we introduced for >> such cases the fallback ZPL license as it fits most the intention of >> somebody contributing to mingw-w64. >> >> Regards, >> Kai > > Ok, I understand. So currently evr.h is in the public domain, but when > I start helping improving it, you will transfer it to ZPL? Wrong, we won't change headers license. > Is there an > option that evr.h remains in PD while I'm helping, so that later it > could be included in mingw headers? It remains PD. Just for juristditations not knowing legal term "public domain", it gets ZPL. For example, German lawsuite doesn't know legal term "public domain". Therefore we introduced ZPL as fallback license for making sure it remains in legal open-source license, if PD isn't usable. > My point is that building MPlayer (which uses mingw) will be *much* > easier that way. > > What do you think? > Regards, Kai |
From: Georgi P. <gog...@gm...> - 2011-02-01 20:50:54
|
On Tue, Feb 1, 2011 at 10:47 PM, Kai Tietz <kti...@go...> wrote: > 2011/2/1 Georgi Petrov <gog...@gm...>: >> On Tue, Feb 1, 2011 at 9:44 PM, Kai Tietz <kti...@go...> wrote: >>> 2011/2/1 Georgi Petrov <gog...@gm...>: >>>> If headers are in public domain, I will be able to include evr.h in >>>> mingw later, but if the headers are ZPL licensed, I wouldn't. >>>> >>>> The problem is that mingw's headers are in the public domain. Is there >>>> any chance that the headers from mingw-w64 are also in public domain >>>> (as is written in the beginning of the current evr.h)? >>> >>> We place headers (not source) into PD. But not in all legislatives >>> there is the term Public Domain usable. Therefore we introduced for >>> such cases the fallback ZPL license as it fits most the intention of >>> somebody contributing to mingw-w64. >>> >>> Regards, >>> Kai >> >> Ok, I understand. So currently evr.h is in the public domain, but when >> I start helping improving it, you will transfer it to ZPL? > Wrong, we won't change headers license. > >> Is there an >> option that evr.h remains in PD while I'm helping, so that later it >> could be included in mingw headers? > It remains PD. Just for juristditations not knowing legal term "public > domain", it gets ZPL. > For example, German lawsuite doesn't know legal term "public domain". > Therefore we introduced ZPL as fallback license for making sure it > remains in legal open-source license, if PD isn't usable. > >> My point is that building MPlayer (which uses mingw) will be *much* >> easier that way. >> >> What do you think? >> > > Regards, > Kai > Kai, thank you very much! This explanation solves all my problems! Greetings! |