Re: [ros-dev] RE: Collection of wine tools on windows

[Boaz Harrosh]

Rolf Kalbermatter wrote:
> This is rubish.

Yes ^ 3 ( that is Yes cubed)

Let us all get back on track of this discussion. Must ReactOS and MinGW 
use the Wine set of headers.

1. ReactOS & MinGW are by themselves GPL, So they are more strict than 
Wine's header set
2. Headers are out of the scope for License as Rolf explained.
    Or to be more precise they are the boundary put by the License. 
"From this API down you are in Library territory".
    The header is the Line drawn by the Library writer, as what is 
public API. A GPL program is an LGPL library with the trivial public 
header of:
    <c> int main(int argc ,char* argc[]) ; // use only </c>
3. Wine Headers are description of the Win32 API by Microsoft, so what 
the hell are you talking about.

And back to the subject. I have proved that Wine-headers are not only, 
nice-to-have, but a must in a gcc compilation environment on Windows, 
like MinGW or Cygwin. Could/did any one see if ReactOS has every thing 
they need in wine-headers and if not patch in the diff.

So is it accepted than!

Free Life
Boaz

[Magnus Olsen]

I do not like to use wine header it exists alot wine specfiy thing in wine
header and alot need to change in the header.
I did need to rewrite alot of wine header to geting directx port of dinput,
dsound and other part. For it did not
exists in MinGW headers. You need alot work to rewrite wine header geting
this working in reactos.
wine header does not work out of the box.  I still think the best choice are
continue to use mingw headers.

----- Original Message ----- 
From: "Boaz Harrosh" [e-mail]
To: "Rolf Kalbermatter" [e-mail];
[e-mail]; [e-mail]
Sent: Wednesday, February 23, 2005 2:43 PM
Subject: Re: [ros-dev] RE: Collection of wine tools on windows
> Rolf Kalbermatter wrote:
> > This is rubish.
>
> Yes ^ 3 ( that is Yes cubed)
>
> Let us all get back on track of this discussion. Must ReactOS and MinGW
> use the Wine set of headers.
> ReactOS & MinGW are by themselves GPL, So they are more strict than
>
> Wine's header set
> 2. Headers are out of the scope for License as Rolf explained.
>     Or to be more precise they are the boundary put by the License.
> "From this API down you are in Library territory".
>     The header is the Line drawn by the Library writer, as what is
> public API. A GPL program is an LGPL library with the trivial public
> header of:
>     <c> int main(int argc ,char* argc[]) ; // use only </c>
> 3. Wine Headers are description of the Win32 API by Microsoft, so what
> the hell are you talking about.
>
> And back to the subject. I have proved that Wine-headers are not only,
> nice-to-have, but a must in a gcc compilation environment on Windows,
> like MinGW or Cygwin. Could/did any one see if ReactOS has every thing
> they need in wine-headers and if not patch in the diff.
>
> So is it accepted than!
>
> Free Life
> Boaz
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Steven Edwards]

--- Magnus Olsen [e-mail] wrote:
> I do not like to use wine header it exists alot wine specfiy thing in wine
> header and alot need to change in the header.
> I did need to rewrite alot of wine header to geting directx port of dinput,
> dsound and other part. For it did not
> exists in MinGW headers. You need alot work to rewrite wine header geting
> this working in reactos.
> wine header does not work out of the box.  I still think the best choice are
> continue to use mingw headers.

I don't think the Wine guys would argue with changing the design of Wines direct
to make it more compatible so we could share the DirectX headers.

Thanks
Steven

__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo

[Thomas Larsen]

Hi All Devs

Problem: BuildNo and Explorer

Could NOT compile reactos with latest mingw package
for new devs to reactos it could be a problem on
the webpage it says just use MingW but only the newest seperate version
of gcc++ from mingw works why not have "Reactos Own MingW Build tools On reactos.com.."
testet tools their work with reactos then no dlltool, compiler and wrong header problems??

Problem: Shlwapi.dll

Complains about undefined refs. to "f1" "f2" "f123" and so on what could the problem be its the
newest svn version and i newer see it before now?

Thomas Larsen

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[Gunnar Dalsnes]

Thomas Larsen wrote:
> Hi All Devs
>
> Problem: BuildNo and Explorer
>
> Could NOT compile reactos with latest mingw package
> for new devs to reactos it could be a problem on
> the webpage it says just use MingW but only the newest seperate version
> of gcc++ from mingw works why not have "Reactos Own MingW Build tools On reactos.com.."

http://reactos.com/wiki/index.php/Build_Environment
> testet tools their work with reactos then no dlltool, compiler and wrong header problems??
>
> Problem: Shlwapi.dll
>
> Complains about undefined refs. to "f1" "f2" "f123" and so on what could the problem be its the
> newest svn version and i newer see it before now?

http://reactos.com/wiki/index.php/Build_Environment
> Thomas Larsen
>
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Ge van Geldorp]

> From: Thomas Larsen
>
> Could NOT compile reactos with latest mingw package
> for new devs to reactos it could be a problem on
> the webpage it says just use MingW but only the newest 
> seperate version of gcc++ from mingw works why not have 
> "Reactos Own MingW Build tools On reactos.com.." testet tools 
> their work with reactos then no dlltool, compiler and wrong 
> header problems??

http://www.reactos.com/en/reactos_developer_site/resources/download_the_reco
mmended_compiler says you need to separately install GCC 3.3.1 and G++ 3.3.1
AFAIK that still works (although most people seem to be using 3.4.2 now)
> Problem: Shlwapi.dll
>
> Complains about undefined refs. to "f1" "f2" "f123" and so on 
> what could the problem be its the newest svn version and i 
> newer see it before now?

Can you edit shlwapi.spec, remove the "-noname" from these lines:

25  stdcall -noname IsCharAlphaWrapW(long) user32.IsCharAlphaW
26  stdcall -noname IsCharUpperWrapW(long) user32.IsCharUpperW
27  stdcall -noname IsCharLowerWrapW(long) user32.IsCharLowerW
28  stdcall -noname IsCharAlphaNumericWrapW(long) user32.IsCharAlphaNumericW

and let us know if it compiles ok then? "older" binutils (before 2.15.94 I
think) have a problem with forwarding in combination with -noname.

Ge van Geldorp.