From: <olo...@te...> - 2005-02-07 19:07:28
|
Hi there. Is there some particular reason to why the header file is so incomplete? Olof |
From: Michael G. <mg...@te...> - 2005-02-07 21:57:05
|
> Is there some particular reason to why the header file is so incomplete? Presumably because so far noone bothered to provide the missing content. =46eel free to complete what's missing (but don't copy from copyrighted code etc.). Best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mg...@te... GPG-keys available on request or at public keyserver |
From: <olo...@te...> - 2005-02-07 22:30:01
|
I am not clever enought to figure out what the missing vfm-macros should look like without reading Microsofts header files from the platform SDK. How exactly would it be possible for me to contribute without copying after that? Are there any guidelines for how such contributions should be written in order to not violate the copy right? ----- Original Message ----- From: "Michael Gerdau" <mg...@te...> To: <min...@li...> Sent: Monday, February 07, 2005 10:56 PM Subject: Re: [Mingw-users] vfw.h |
From: Michael G. <mg...@te...> - 2005-02-07 22:48:27
|
> I am not clever enought to figure out what the missing vfm-macros should= =20 > look like > without reading Microsofts header files from the platform SDK. That's probably not allowed to be a source for w32api... > How exactly =20 > would it be possible for me to contribute without copying after that? I _think_ reading the MSDN documentation and deriving the missing parts from there is OK. But I don't know for certain. However reading http://www.mingw.org/bugs.shtml seems to indicate reading MSDN is OK. Maybe the website should provide instructions as to what must not be done and what is acceptable ? > Are there any guidelines for how such contributions should be written in= =20 > order > to not violate the copy right? I'm only aware of the obvious ones: a) don't copy from existing copyrighted code. b) all you come up with yourself and that is not subject to a) above should be fine. As an amendment to a) there are some OpenSource licences for which copying would be acceptable. For details you should ask on a case by case basis. Best, Michael =2D-=20 Vote against SPAM - see http://www.politik-digital.de/spam/ Michael Gerdau email: mg...@te... GPG-keys available on request or at public keyserver |
From: Earnie B. <ea...@us...> - 2005-02-08 12:21:11
|
<quote who="Olof TÃ¥ngrot"> > I am not clever enought to figure out what the missing vfm-macros should > look like > without reading Microsofts header files from the platform SDK. How exactly > would it be possible for me to contribute without copying after that? > Search MSDN for documentation. Determine what you want to use and supply only the parts of interest to you. Then later you might add other missing features. > Are there any guidelines for how such contributions should be written in > order > to not violate the copy right? > Find as much public information in the form of documentation that you can find and use the documentation to create your source. That is the only method to not violate the copyright. Documentation does not include source code examples, the source code example is still source that you would copy. If you can't find the documentation to fullfill all you need say constant definitions for example, then trial and error or find a partner to write the documentation and make it available publicly. Earnie -- http://www.mingw.org http://sourceforge.net/projects/mingw https://sourceforge.net/donate/index.php?user_id=15438 |
From: <olo...@te...> - 2005-02-08 21:33:18
|
Would it be Ok to use macros that expands to the copyrighted definitions? ----- Original Message -----=20 From: "Earnie Boyd" <ea...@us...> To: <min...@li...> Sent: Tuesday, February 08, 2005 1:21 PM Subject: Re: [Mingw-users] vfw.h > <quote who=3D"Olof T=C3=A5ngrot"> >> I am not clever enought to figure out what the missing vfm-macros shou= ld >> look like >> without reading Microsofts header files from the platform SDK. How=20 >> exactly >> would it be possible for me to contribute without copying after that? >> > > Search MSDN for documentation. Determine what you want to use and supp= ly > only the parts of interest to you. Then later you might add other miss= ing > features. > >> Are there any guidelines for how such contributions should be written= in >> order >> to not violate the copy right? >> > > Find as much public information in the form of documentation that you c= an > find and use the documentation to create your source. That is the only > method to not violate the copyright. Documentation does not include > source code examples, the source code example is still source that you > would copy. If you can't find the documentation to fullfill all you ne= ed > say constant definitions for example, then trial and error or find a > partner to write the documentation and make it available publicly. > > Earnie > > -- > http://www.mingw.org > http://sourceforge.net/projects/mingw > https://sourceforge.net/donate/index.php?user_id=3D15438 > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users= . > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users=20 |