André Hentschel writes:
> @@ -2569,6 +2570,7 @@ sub generate_project_files($)
> print FILEO "\$(${canon}_MODULE).so: \$(${canon}_OBJS)
> \$(${canon}_MODULE:.dll=.def)\n";
>} elsif (@$target[$T_TYPE] == $TT_DLL) {
> print FILEO "\$(${canon}_MODULE).so: \$(${canon}_OBJS)
André Hentschel writes:
> @@ -2576,7 +2577,9 @@ sub generate_project_files($)
>if (@$target[$T_TYPE] == $TT_DLL && (@$project_settings[$T_FLAGS] &
> $TF_HASDEF)) {
> print FILEO "\$(${canon}_MODULE).so: \$(${canon}_OBJS)
> \$(${canon}_MODULE:.dll=.def)\n";
>} elsif (@$t
Am 19.11.2011 20:18, schrieb Vitaliy Margolen:
> On 11/19/2011 11:42 AM, André Hentschel wrote:
>> this catches more than one 0 after the space and possible 0s after the x
>> +if (/[[:space:]]0+x0*101$/) {
> For more then one you should use "+" not "*". "*" means any number, includi
On 11/19/2011 11:42 AM, André Hentschel wrote:
this catches more than one 0 after the space and possible 0s after the x
+if (/[[:space:]]0+x0*101$/) {
For more then one you should use "+" not "*". "*" means any number, including 0.
Vitaliy
On 11/14/2011 04:04 AM, Francois Gouget wrote:
On Fri, 11 Nov 2011, André Hentschel wrote:
seen some "broken" project files which still worked with msvc but not with
winemaker
---
tools/winemaker |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --g
On Fri, 11 Nov 2011, André Hentschel wrote:
> seen some "broken" project files which still worked with msvc but not with
> winemaker
> ---
> tools/winemaker |8
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/tools/winemaker b/
André Hentschel writes:
> @@ -2480,7 +2498,9 @@ sub generate_project_files($)
>my $canon=canonize("@$target[$T_NAME]");
>$canon =~ s/_so$//;
>
> - if (@$target[$T_TYPE] == $TT_DLL) {
> + if (@$target[$T_TYPE] == $TT_DLL && (@$project_settings[$T_FLAGS] &
> $TF_HASDEF)
André Hentschel wrote:
---
tools/winemaker |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
Hi André,
Not a comment on the patch itself but this is the third time you tried
with the same patch.
We
Austin English schrieb:
On Thu, Apr 2, 2009 at 2:58 PM, Dawncrow wrote:
---
tools/winemaker | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
Your patch lacks your real name.
Sry for the noise, selected the wrong account, the four patches after
these are
On Thu, Apr 2, 2009 at 2:58 PM, Dawncrow wrote:
> ---
> tools/winemaker | 10 +-
> 1 files changed, 5 insertions(+), 5 deletions(-)
>
>
>
>
>
>
Your patch lacks your real name.
--
-Austin
other words, the following does not work:
winemaker Chap03/HelloWin/HelloWin.dsw
--
Francois Gouget http://fgouget.free.fr/
Demander si un ordinateur peut penser revient à demander
si un sous-marin peut nager.
This one is wrapped too.
But the main problem is that it does not handle case fixes. This can be
fixed by applying the attached patch on top of it.
With this, if you go test with the Programming Windows 98 samples, the
following scenario works:
cd Chap03/HelloWin
winemaker HelloWin.dsp
This one is wrapped. Besides that it's ok, so if you resubmit it should
go in.
--
Francois Gouget http://fgouget.free.fr/
$live{free} || die "";
Hello,
Francois can you agree with these patches?
http://www.winehq.org/pipermail/wine-patches/2009-March/070560.html
http://www.winehq.org/pipermail/wine-patches/2009-March/070561.html
http://www.winehq.org/pipermail/wine-patches/2009-March/070562.html
http://www.winehq.org/pipermail/wine-patches
Here are some quick comments:
You cannot add functions that are not used. So this patch should include
the following lines from patch 0004:
+if (defined $opt_work_dir) {
+# Now scan the directory tree looking for source files and, maybe,
targets
+print "Scanning the source
It works great! So IMHO it can be used.
The two changes are independent so they should be in separate patches.
About afxres.h vs. winres.h vs. winresrc.h, I believe it's mostly
IDC_STATIC that was needed from winres.h. Unfortunately it's not being
defined anywhere these days. In fact, all the Microsoft samples define
it themselves.
ld be put
in both (except -fexceptions which seems to be on by default in C++,
but that's minor).
About the commented out call to fix_file_and_directory_names(), I don't
think winemaker should go and modify files outside of '.'. So I think
it's safe to remove this call ent
André Hentschel wrote:
>
>
Changes the spacing of the entire file.
Also, if you are going to take this time, change indenting to two or four per
level.
James McKenzie
Hi,
it seems like the open function failed, but the error code wasn't
checked, resulting in a wrong filehandle. I think I would correct it
this way (see attached patch).
Regards,
Colin Pitrat (Bull Services Telco)
Bull, Architect of an Open World (TM)
Tél : +33 (0) 1 30 80 72 93
www.bull.co
Now I am running it on a latest GIT tree this way:
$ tools/winapi/msvcmaker --no-wine
.: searching for /^Makefile.in$/
And after a while it appends this string to the end of last line:
readline() on closed filehandle IN at tools/winapi/msvcmaker line 134.
Maybe it doesn't indicate any harm,
Am Dienstag, 11. April 2006 22:43 schrieben Sie:
> In KDevelop, did you set up a new project your ddraw test app? If so, which
> type did you pick? Thanks.
I think I picked a c++ console project.
Stefan
pgp5JeZoMJiW7.pgp
Description: PGP signature
In KDevelop, did you set up a new project your ddraw test app? If so, which
type did you pick? Thanks.
-Original Message-
From: Stefan Dِsinger [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 23, 2006 9:27
To: wine-devel@winehq.org; Ng, Billy H CIV NAVSEA
Subject: Re: IDE with Winemaker
On Wed, 22 Mar 2006 15:58:13 -0500, Ng, Billy H CIV NAVSEA wrote:
> Hi, I am a Windows Developer who is new to the Linux world.
> Is there any IDE (like Visio Studio) I can use with Winemaker? I am
> trying to port a Windows App to Linux Fedora.
Heya,
On Linux the usage of IDEs is
Hi,
> Hi, I am a Windows Developer who is new to the Linux world. Is there any
> IDE (like Visio Studio) I can use with Winemaker? I am trying to port a
> Windows App to Linux Fedora.
I managed to use wineg++ with kdevelop by overriding the compiler. It worked
quite well for my needs(cod
Title: IDE with Winemaker
Hi, I am a Windows Developer who is new to the Linux world. Is there any IDE (like Visio Studio) I can use with Winemaker? I am trying to port a Windows App to Linux Fedora.
Thanks,
Billy.
support in Winelib but none that were
deemed good enough to be committed to CVS.
Below is a technique I use in C++. I'm not sure it can be used in C. But
if you have C++ it is perfect. And nothing needs done in Winemaker Just
have the #define available before the using code like in your
Hi,
--- Francois Gouget <[EMAIL PROTECTED]> wrote:
> > 4) Would there be a way to transform __try {}/__finally{} blocks to
> > __TRY {}/__FINALLY()? I'm not sure the changes I did are now compilable
> > under MSVC nor MingW.
>
> Unfortunately they don't work exactly the same. There has been many
On Sat, 18 Feb 2005, Vincent Béron wrote:
Hi François,
I tried to use winemaker on an app, and I had the following notes about
it.
1) Some subdirs were not visited by winemaker, while some others were.
Should it visit all of them recursively? Does it stops if there are no
source file in a dir (but
Hi François,
I tried to use winemaker on an app, and I had the following notes about
it.
1) Some subdirs were not visited by winemaker, while some others were.
Should it visit all of them recursively? Does it stops if there are no
source file in a dir (but there are subdirs)? The last point
Scott,
On Wednesday 15 December 2004 06:32, Scott Ritchie wrote:
> Global symbol "%directories" requires explicit package name
> at /usr/bin/winemaker line 423.
> Global symbol "%directories" requires explicit package name
> at /usr/bin/winemaker line 441.
&
On Tue, 14 Dec 2004 21:32:26 -0800, Scott Ritchie <[EMAIL PROTECTED]> wrote:
> As part of my effort to create a successful demonstration of how to port
> something, I tried out winelib. Unfortunately, I can't seem to get it
> working at all. I get this error whenever I run wi
As part of my effort to create a successful demonstration of how to port
something, I tried out winelib. Unfortunately, I can't seem to get it
working at all. I get this error whenever I run winemaker:
Global symbol "%directories" requires explicit package name
at /usr/bin/win
Hi,
i want to compile a small MFC based app using winelib/winemaker. The system is
Debian SID (upto date, daily patched) (wine 20040716).
As I understood from doc 'winelib-user/mfc-compiling' I have to compile MFC
first. I copied dir 'atlmfc' from VC7 onto my machine, cd&
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
<[EMAIL PROTECTED]> wrote:
> On Friday 03 September 2004 07:18 am, you wrote:
> > On Thu, 2 Sep 2004, Patrick Goupell wro
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
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 Mic
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
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
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 Wi
oking 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 scanni
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
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 tas
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?
winemaker. It gives me the following error:
make[1]: Entering directory `//src'makefile:1: *** missing separator. Stop.make[1]: Leaving directory `//src'make: *** [src] Error 2
-- Veerendra.
Vincent Béron <[EMAIL PROTECTED]> wrote:
Le mar 10/08/2004 à 19:39, Veerendra Tippa
Le mar 10/08/2004 à 19:39, Veerendra Tippanagoudar a écrit :
> Hi,
>
> I am trying to port a project from windows to unix. I have installed redhat 7.0.
> After installing wine, i tried using winemaker on a set of modules that are
> interdependent.
> By modules, I mean sub-pr
Hi,
I am trying to port a project from windows to unix. I have installed redhat 7.0.
After installing wine, i tried using winemaker on a set of modules that are interdependent.
By modules, I mean sub-programs. When I run winemaker from the top of the project directory, it creates only Makefile
> of code allowed for by other compilers? Or document the changes that
> you will run in to porting C++ from other compilers?
Detecting this kind of problem would require us to have a C++
parser which is more than intended for winemaker.
So we could document it though, imho, the g++ error message i
On Sun, Jun 20, 2004 at 01:36:15PM +0300, Shachar Shemesh wrote:
> Shachar Shemesh wrote:
>
> I managed to solve the above problem by adding a "-shared name.spec" to
> the Makefile line that invokes the last winegcc. However, I think
> winemaker should have added that l
the following content in it:
@ cdecl func( long )
In this directory, run "winemaker --dll ."
Run "make".
I would expect, at this stage, to get a file called "name.dll.so".
Instead, I get a file called "name.dll.exe.so", with which I cannot
link other appli
in it:
@ cdecl func( long )
In this directory, run "winemaker --dll ."
Run "make".
I would expect, at this stage, to get a file called "name.dll.so".
Instead, I get a file called "name.dll.exe.so", with which I cannot link
other applications, even if I tr
r compilers?
2. Winemaker does not import all of the import libs from the MS_VC
makefile. When building my projects it does not link to ddraw even
though the MS_VC makefile has ddraw.lib in it. So I will get the
following warning on linking:
winmain.o(.text+0xd5): In function `DoModeEnumeration(HWND_
On Wed, Jun 02, 2004 at 02:07:16PM +0200, Ahmed Abdel Aal wrote:
> Hi,
> I installed new version of wine -20040505 but when I tried
> to use winemaker to gnerate configuration file.
> it is not generated and generate Makefile direct.
> is it and error in winemaker or updates
Hi,
I installed new version of wine
-20040505 but when I tried
to use winemaker to gnerate configuration
file.
it is not generated and generate Makefile
direct.
is it and error in winemaker or updates in new
version.
thanks
aallabs
:
winemaker -A 'DEFS=-DSTRICT ...'
where -A will simply add the argument as a line at the beginning of
the generated Makefile. This is easier to implement, document, etc.,
and it's general enough that we don't have to keep adding options
to support all sorts of users.
Be
On April 3, 2004 6:43 pm, Francois Gouget wrote:
> I agree on the A/B distinction. However even in the B case we need these
> options for those cases where winemaker generates a whole lot of
> makefiles.
Right. We need to support that case, but it seems that we need a way
to include stu
on like this
> is just dangerous. So for this case we don't need those
> options either, the user can simply edit the resulting Makefile
> and add them in there just as easily.
I agree on the A/B distinction. However even in the B case we need these
options for those cases where winem
On April 2, 2004 4:01 pm, Francois Gouget wrote:
> These options are global, i.e. they are supposed to be effective in
> every makefile makefile generated by winemaker. For this reason they
> used to go in the Make.rules.in file. That way one could later modify
> them in one plac
On Fri, 2 Apr 2004, Bill Medland wrote:
[...]
> What I used toi have was:
> #! /bin/bash
> # Run this script in order to pass the correct arguments to winemaker so that
> # it can set up the build environment
> winemaker --nosource-fix --nogenerated-specs --dll --single-target myt
I haven't been following the winemaker stuff so I don't know whether it is
supposed to be able to handle this (and is broken) or not.
I am having to play with the "build a builtin dll to wrap a linux so" concept
again after a year or so since the last time, as discussed i
On Tue, 2 Mar 2004, Dimitrie O. Paun wrote:
> On Tue, 2 Mar 2004, Francois Gouget wrote:
[...]
> >We must specify '-lmsvcrt' if using the msvcrt.
>
> Please don't, it's not needed. If you want to use msvcrt, please
> pass the -mno-cygwin switch. if that doesn' work, it's a bug
> in winegcc.
A
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
>> 6. winegcc is not rebuilt if the '--prefix' changes.
>
> Maybe AJ can fix the Makefile. I think winegcc.o should depend on
> the Makefile.
Nothing gets rebuilt if the prefix changes, you have to do a make
clean.
--
Alexandre Julliard
[EMAIL PROT
On Tue, 2 Mar 2004, Francois Gouget wrote:
> winemaker is pretty broken since it has been patched to call winegcc. I
> suspect it was not tested.
Hey, I can't do everything! :))) I just wanted to get the ball rolling.
>We must specify '-lmsvcrt' if using the msvcrt.
On Fri, 27 Feb 2004, Francois Gouget wrote:
> Does winegcc systematically link applications and dlls to advapi32,
> comdlg32, etc? How does one do if one does not want to link with gdi32
> for instance?
Yes, it does, those are the defaults for MinGW. More specifically,
all apps are linked by defa
On Fri, 27 Feb 2004, Dimitrie O. Paun wrote:
[...]
> @@ -801,7 +753,7 @@
> $basename=~ s/\.(dll|exe)$//i;
> # This is the default link list of Visual Studio, except odbccp32
> # which we don't have in Wine.
> -my @std_imports=qw(advapi32 comdlg32 gdi32 kernel32 odbc32 ole32 oleau
65 matches
Mail list logo
