winemaker

[Patrick Goupell]

I was looking at the development tasklets for something I might be able to do.

I noticed bug #230 - winemaker: Extract more information from the source 
files.

How do I make known my interest in attempting to do this task?

[Francois Gouget]

On Tue, 31 Aug 2004, Patrick Goupell wrote:
> I was looking at the development tasklets for something I might be able to do.
>
> I noticed bug #230 - winemaker: Extract more information from the source
> files.
>
> How do I make known my interest in attempting to do this task?

Seems like you just did<g>.
If you want to work on it go ahead as noone else is working on it as far
as I know.

[Patrick Goupell]

The bug description mentions looking at the *.c and *.cpp source looking for 
main, WinMain and DllMain.  Looking at the  *.h source and looking for 
#pragma comment(lib, 'foo.lib').

Is there anything else I should be looking for while I attempt this?
> On Tuesday 31 August 2004 08:38 pm, you wrote:
> On Tue, 31 Aug 2004, Patrick Goupell wrote:
> > I was looking at the development tasklets for something I might be able
> > to do.
> >
> > I noticed bug #230 - winemaker: Extract more information from the source
> > files.
> >
> > How do I make known my interest in attempting to do this task?
>
> Seems like you just did<g>.
> If you want to work on it go ahead as noone else is working on it as far
> as I know.

[Francois Gouget]

On Wed, 1 Sep 2004, Patrick Goupell wrote:
> The bug description mentions looking at the *.c and *.cpp source looking for
> main, WinMain and DllMain.  Looking at the  *.h source and looking for
> #pragma comment(lib, 'foo.lib').
>
> Is there anything else I should be looking for while I attempt this?

These are the only thing I remember from when I worked on winemaker.
What's most likely is that you'll find winemaker a bit broken as the way
to build Winelib applications has changed a lot and winemaker may not
have completely caught up.

Tip: This scanning can probably be done in fix_file().
(I'm just hoping it's not a bad tip)

[Patrick Goupell]

On Wednesday 01 September 2004 11:22 pm, you wrote:
> On Wed, 1 Sep 2004, Patrick Goupell wrote:
> > The bug description mentions looking at the *.c and *.cpp source looking
> > for main, WinMain and DllMain.  Looking at the  *.h source and looking
> > for #pragma comment(lib, 'foo.lib').
> >
> > Is there anything else I should be looking for while I attempt this?
>
> These are the only thing I remember from when I worked on winemaker.
> What's most likely is that you'll find winemaker a bit broken as the way
> to build Winelib applications has changed a lot and winemaker may not
> have completely caught up.
>
> Tip: This scanning can probably be done in fix_file().
> (I'm just hoping it's not a bad tip)

Is there a repository where I can get some projects to test my changes to 
winemaker?

[Francois Gouget]

On Thu, 2 Sep 2004, Patrick Goupell wrote:
[...]
> Is there a repository where I can get some projects to test my changes to
> winemaker?

What I've done in the past is grab the examples that come with Windows
programming books, typically the Petzolds.
Besides that you may try the open-source projects mentioned on Wine's
Winelib page, which is the closest thing we have to a Winelib repository
of test applications:

http://www.winehq.org/site/winelib

[Francois Gouget]

On Thu, 2 Sep 2004, Patrick Goupell wrote:
[...]
> Is there a repository where I can get some projects to test my changes to
> winemaker?

Here are a couple more ideas:

* the Microsoft Platform SDK also comes with a lot of samples that you
could use to exercise winemaker. However I didn't try them and they are
probably more likely than other bits of code to contain Microsoft-isms
that gcc is going to choke on.

* the Virtual X Class Library (VXCL) contains a number of samples that
may be usable too.
   http://www.toddtown.com/Index.php?pageID=Home/Index

[Andreas Mohr]

Hi,

On Fri, Sep 03, 2004 at 01:18:42PM +0200, Francois Gouget wrote:
> On Thu, 2 Sep 2004, Patrick Goupell wrote:
> [...]
> > Is there a repository where I can get some projects to test my changes to
> > winemaker?
>
> Here are a couple more ideas:
> - the Microsoft Platform SDK also comes with a lot of samples that you
>
> could use to exercise winemaker. However I didn't try them and they are
> probably more likely than other bits of code to contain Microsoft-isms
> that gcc is going to choke on.

-fms-extensions might help here...
(although in general you should try to get rid of non-standard syntax
as much as possible, I think)

Andreas Mohr

[Patrick Goupell]

On Friday 03 September 2004 07:18 am, you wrote:
> On Thu, 2 Sep 2004, Patrick Goupell wrote:
> [...]
> > Is there a repository where I can get some projects to test my changes to
> > winemaker?
>
> Here are a couple more ideas:
> - the Microsoft Platform SDK also comes with a lot of samples that you
>
> could use to exercise winemaker. However I didn't try them and they are
> probably more likely than other bits of code to contain Microsoft-isms
> that gcc is going to choke on.
> - the Virtual X Class Library (VXCL) contains a number of samples that
>
> may be usable too.
>    http://www.toddtown.com/Index.php?pageID=Home/Index

I have made my changes to winemaker.

I am now trying to do the winemaker, configure, make steps.

This is my first time doing winemaker, configure, make so I am really guessing 
as to what is going on here.

The winemaker and configure steps appear to run.

The make step cannot find the mfc include path.

I have used: winemaker --mfc -I/mvs/cv98/include --lower-all .  (my copy of 
the mfc visual studio include directory)

but get the foloowing errors out of make:
stdafx.h:15:64: afxwin.h: No such file or directory
stdafx.h:16:46: afxext.h: No such file or directory
stdafx.h:17:54: afxdisp.h: No such file or directory
stdafx.h:18:87: afxdtctl.h: No such file or directory
stdafx.h:20:83: afxcmn.h: No such file or directory
stdafx.h:22:23: htmlhelp.h: No such file or directory
stdafx.h:24:20: afxdao.h: No such file or directory
stdafx.h:25:19: afxdb.h: No such file or directory
(and many more of the same)

1.  what should my directory structure be for the program source and mfc 
include files be?  Under one tree or different trees?

2.   Have I entered the correct winemaker command or not?

I get the same results using the original unmodified winemaker script so I 
have to assume that I do not have my winemaker command and/or directory 
structure correct.

Looking for guidance on how to proceed.

[James Hawkins]

> but get the foloowing errors out of make:
> stdafx.h:15:64: afxwin.h: No such file or directory
> stdafx.h:16:46: afxext.h: No such file or directory
> stdafx.h:17:54: afxdisp.h: No such file or directory
> stdafx.h:18:87: afxdtctl.h: No such file or directory
> stdafx.h:20:83: afxcmn.h: No such file or directory
> stdafx.h:22:23: htmlhelp.h: No such file or directory
> stdafx.h:24:20: afxdao.h: No such file or directory
> stdafx.h:25:19: afxdb.h: No such file or directory
> (and many more of the same)

Do those headers appear exactly that way in your include folder ie
case?  This is just a guess, but maybe you could run winemaker in the
directory of the mfc headers.

On Wed, 15 Sep 2004 14:54:52 -0400, Patrick Goupell
 wrote:
> On Friday 03 September 2004 07:18 am, you wrote:
> > On Thu, 2 Sep 2004, Patrick Goupell wrote:
> > [...]
> > > Is there a repository where I can get some projects to test my changes to
> > > winemaker?
> >
> > Here are a couple more ideas:
> > - the Microsoft Platform SDK also comes with a lot of samples that you
> >
> > could use to exercise winemaker. However I didn't try them and they are
> > probably more likely than other bits of code to contain Microsoft-isms
> > that gcc is going to choke on.
> > - the Virtual X Class Library (VXCL) contains a number of samples that
> >
> > may be usable too.
> >    http://www.toddtown.com/Index.php?pageID=Home/Index
>
> I have made my changes to winemaker.
>
> I am now trying to do the winemaker, configure, make steps.
>
> This is my first time doing winemaker, configure, make so I am really guessing
> as to what is going on here.
>
> The winemaker and configure steps appear to run.
>
> The make step cannot find the mfc include path.
>
> I have used: winemaker --mfc -I/mvs/cv98/include --lower-all .  (my copy of
> the mfc visual studio include directory)
>
> but get the foloowing errors out of make:
> stdafx.h:15:64: afxwin.h: No such file or directory
> stdafx.h:16:46: afxext.h: No such file or directory
> stdafx.h:17:54: afxdisp.h: No such file or directory
> stdafx.h:18:87: afxdtctl.h: No such file or directory
> stdafx.h:20:83: afxcmn.h: No such file or directory
> stdafx.h:22:23: htmlhelp.h: No such file or directory
> stdafx.h:24:20: afxdao.h: No such file or directory
> stdafx.h:25:19: afxdb.h: No such file or directory
> (and many more of the same)
> - what should my directory structure be for the program source and mfc
>
> include files be?  Under one tree or different trees?
> - Have I entered the correct winemaker command or not?
>
> I get the same results using the original unmodified winemaker script so I
> have to assume that I do not have my winemaker command and/or directory
> structure correct.
>
> Looking for guidance on how to proceed.