Hi there,
I wanted to implement some gdiplus functions, but for this I need the GUIDs of some properties.
I took the GUIDs from http://www.reactos.org/generated/doxygen/db/de2/gdiplusimaging_8h-source.htm...,
but when I tried to compile gdiplus with the new gdiplusimaging.h with many DEFINE_GUID's,
the compiler kept complaining that "hidden symbol `FrameDimensionPage' isn't defined".
What did I do wrong?
-Adam
On Jan 19, 2008 7:58 AM, Adam Rimon adamrimon@gmail.com wrote:
Hi there,
I wanted to implement some gdiplus functions, but for this I need the GUIDs of some properties.
I took the GUIDs from http://www.reactos.org/generated/doxygen/db/de2/gdiplusimaging_8h-source.htm...,
but when I tried to compile gdiplus with the new gdiplusimaging.h with many DEFINE_GUID's,
the compiler kept complaining that "hidden symbol `FrameDimensionPage' isn't defined".
What did I do wrong?
Don't copy code from ReactOS and submit it to Wine.
James Hawkins wrote:
On Jan 19, 2008 7:58 AM, Adam Rimon adamrimon@gmail.com wrote:
Hi there,
I wanted to implement some gdiplus functions, but for this I need the GUIDs of some properties.
I took the GUIDs from http://www.reactos.org/generated/doxygen/db/de2/gdiplusimaging_8h-source.htm...,
but when I tried to compile gdiplus with the new gdiplusimaging.h with many DEFINE_GUID's,
the compiler kept complaining that "hidden symbol `FrameDimensionPage' isn't defined".
What did I do wrong?
Don't copy code from ReactOS and submit it to Wine.
Adam:
It is not permitted (and I don't know or care to know the reason why), code from the ReactOS project and attempt to put it in the Wine project.
You will have to make, from the ground up, new code. However, if you attempt to submit it, these changes may be rejected in the future.
James McKenzie (I am not allowed to submit code because I have an active MSDN subscription which gives me access to Windows and Windows project source code.)
On 01/19/2008 08:24 PM, James McKenzie wrote:
James Hawkins wrote:
On Jan 19, 2008 7:58 AM, Adam Rimon adamrimon@gmail.com wrote:
Hi there,
I wanted to implement some gdiplus functions, but for this I need the GUIDs of some properties.
I took the GUIDs from http://www.reactos.org/generated/doxygen/db/de2/gdiplusimaging_8h-source.htm...,
but when I tried to compile gdiplus with the new gdiplusimaging.h with many DEFINE_GUID's,
the compiler kept complaining that "hidden symbol `FrameDimensionPage' isn't defined".
What did I do wrong?
Don't copy code from ReactOS and submit it to Wine.
Adam:
It is not permitted (and I don't know or care to know the reason why), code from the ReactOS project and attempt to put it in the Wine project.
You will have to make, from the ground up, new code. However, if you attempt to submit it, these changes may be rejected in the future.
James McKenzie (I am not allowed to submit code because I have an active MSDN subscription which gives me access to Windows and Windows project source code.)
Well, right now I don't send it to Wine. I just want to define a GUID in gdiplusimaging.h. My question is about adding a GUID to a header file and compile it, not about the GUIDs themselves.
On Jan 19, 2008 1:24 PM, James McKenzie jjmckenzie51@sprintpcs.com wrote:
James McKenzie (I am not allowed to submit code because I have an active MSDN subscription which gives me access to Windows and Windows project source code.)
Now the real question I have is, are you not allowed to ever contribute code to Wine ever again even if you cancel your MSDN subscription and swear before King and Country that you no longer have access to Windows code....
James McKenzie
(I am not allowed to submit code because I have an active MSDN subscription which gives me access to Windows and Windows project source code.)
I haven't had an MSDN subscription in a while but I think it would be very strange that it comes with Windows source code. The most I have seen is the crt source code from the Visual Studio Development systems (and there would be the MFC source code too I suppose, but I couldn't care about that less) although I never really cared to dig into the crt and only ever really got into it more by accident when deugging my own code and single stepping into a runtime function, which is mostly more a pain than anything else.
My understanding is that the fact that I had the possibility to look at the crt code would at most prevent me to submit patches to msvcrt and friends but not to Wine as a whole.
Why an MSDN subsciption should prevent someone from submitting any code to Wine is beyond me, but maybe they changed the EULA of it?? (Which I would suspect would not hold in court because of antitrust concerns).
Or did they really start to ship source code with it? I simply can't believe they would ship ntdll.dll or ntos.exe or other core DLL source code ever.
Rolf Kalbermatter
On Jan 20, 2008 7:34 AM, Rolf Kalbermatter r.kalbermatter@hccnet.nl wrote:
Why an MSDN subsciption should prevent someone from submitting any code to Wine is beyond me, but maybe they changed the EULA of it?? (Which I would suspect would not hold in court because of antitrust concerns).
Or did they really start to ship source code with it? I simply can't believe they would ship ntdll.dll or ntos.exe or other core DLL source code ever.
MSDNAA Subscriber downloads like for university students contain the source for ntos. Microsoft hired Dave Probert to put together the Windows Academic Program and University Source Licenses where they give away like 90% of the core system to push universities to use it to teach operating system design. As I don't have a MSDNAA account I don't know how much of the system is really there but the source license terms are very liberal. i.e. You can learn from it but not copy any code from it, any ideas you take with you are not restricted,etc. I have a friend in the program so I will ask him if it includes any of the Win32 api, but I doubt it.
-
Adam Rimon -
James Hawkins -
James McKenzie -
Rolf Kalbermatter -
Steven Edwards