On September 29, 2003 03:33 pm, Alexandre Julliard wrote:
> No it won't, that's why we need to change bin2res to generate only a
> single file at a time, otherwise it breaks parallel makes.
OK, how about this:
ChangeLog
Teach bin2res to deal with one file at a time.
Index: tools/bin2res.c
==
I am still lacking the need to have this script. If someone really
wants to build parts of WINE on Windows we should really only support
MSYS+Mingw or MS_VC. I dont think there are that many people that want
to build WINE programs that need extra help. I can try to write better
documentation for th
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> The one intermediate file is needed for separating the rules in
> Make.rules and the dependencies in 'make depend'. This also allows
> it to work with multiple .rc files just fine.
As long as the .rc file is the one you build the .res from, but tha
On Mon, 29 Sep 2003, Alexandre Julliard wrote:
> We need a way for bin2res to extract a single file for this to work
> right. And yes, it only works if all the binaries are in a single rc
> file which happens to be the main rc file, otherwise you need to write
> multiple rules manually.
Right, t
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> All that to avoid a dummy file?!? But anyway, you did not answer
> my question :) Can you describe what you have in mind, like giving
> an example of how you want to handle it, so I can better understand
> where you're comming from?
To take comctl3
On Mon, 29 Sep 2003, Alexandre Julliard wrote:
> I don't necessarily think it's simpler, but it's less ugly. We
> definitely don't want to create dummy intermediate files. But yes in
> the complex cases we may have to write the rules by hand; I don't
> think that's a big deal, there aren't that ma
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> The only complication here is the .extract file which
> allows us to split the dependencies from the rules.
> The complicated stuff are the dependencies, but you
> need those anyway. A simple marker file is a small
> price to pay for the convenience
> I don't think that's a real problem, these files don't change
> often. It certainly doesn't justify adding a complicated
> infrastructure to deal with it.
Indeed, I said, and I let it go. But thinking a little more
about it, I don't see how you solve the problem with the
manual stuff. As I under
> > I was not aware of that because I always got WRC error messages like
> > "explorer_intres.rc:337:58: Error: Cannot handle UNICODE filenames"
> > when using
> > IDI_EXPLORERICONDISCARDABLE "res/explorer.ico"
> >
> > Now I tried once more and found this works:
> > IDI_EXPLORER
Martin Fuchs <[EMAIL PROTECTED]> writes:
> I was not aware of that because I always got WRC error messages like
> "explorer_intres.rc:337:58: Error: Cannot handle UNICODE filenames"
> when using
> IDI_EXPLORERICONDISCARDABLE "res/explorer.ico"
>
> Now I tried once more and foun
On Sun 28. September 2003 04:23, Alexandre Julliard wrote:
> Martin Fuchs <[EMAIL PROTECTED]> writes:
> > I tried to compile my explorer as winelib application, and got to this
> > problem: How to compile a resource file, which has no problems with RC or
> > WINDRES with WRC?
>
> If it compiles wit
Martin Fuchs <[EMAIL PROTECTED]> writes:
> I tried to compile my explorer as winelib application, and got to this
> problem: How to compile a resource file, which has no problems with RC or
> WINDRES with WRC?
If it compiles with rc and windres then it should compile with wrc
too. The inline st
On Wed 24. September 2003 06:08, Dimitrie O. Paun wrote:
> > Some resource files refer to icons if __WINE__ is not defined. The icons
> > are missing. Perhaps those references can be removed. Alternatively,
> > icon resources should be converted to the binary format in Wine. I don't
> > know if
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> Yeah, but if we do that we'll have to maintain them manually.
I don't think that's a real problem, these files don't change
often. It certainly doesn't justify adding a complicated
infrastructure to deal with it.
--
Alexandre Julliard
[EMAIL PROT
On Thu, 25 Sep 2003, Steven Edwards wrote:
> Maybe I missed something here but why do you need bin2res at all? WRC
> can compile the resources to be linked by windres/MS_VC. We have the
> #ifdef WINE in regedit because the ReactOS people are lazy and havent
> merged wrc in to our CVS yet. I build
On Thu, 25 Sep 2003, Alexandre Julliard wrote:
> I thought you were talking about doing it in make depend, and this
> won't work. Now if you want to generate it directly into the
> Makefile.in then of course that's possible, but I don't think we want
> to generate rules, these belong in Make.rules
Maybe I missed something here but why do you need bin2res at all? WRC
can compile the resources to be linked by windres/MS_VC. We have the
#ifdef WINE in regedit because the ReactOS people are lazy and havent
merged wrc in to our CVS yet. I build these applications all the time
on Windows using MSY
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> I'm definitely missing something here. I figured that if we
> have a file called rsrc.rc with 3 embedded bitmaps in it called
> bitmap[123].bmp, we need a rule like so:
>
> bitmap1.bmp bitmap2.bmp bitmap3.bmp: rsrc.rc
> bin2res !<
>
> That can
On September 24, 2003 07:02 pm, Alexandre Julliard wrote:
> I don't really see how you would do that, especially not to make it do
> the right thing on make clean etc. I think we'll just want to list the
> files manually.
I'm definitely missing something here. I figured that if we
have a file call
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> Well, dependencies are not a problem: I can modify bin2res to output
> the name of the dependencies, and then 'make depend' can include
> them just like it does with the others...
I don't really see how you would do that, especially not to make it
On Wed, 24 Sep 2003, Alexandre Julliard wrote:
> Yes that's the right way to do it. The only drawback is that we will
> need to list the dependencies explicitly in the makefile; but we need
> that to really support other resource compilers anyway.
Well, dependencies are not a problem: I can modif
Hello Pavel,
You can build the programs only also using the makefiles. You dont need
to use WINEs dlls or import libs. You can just run make programs or cd
to programs and type make.
Thanks
Steven
--- Pavel Roskin <[EMAIL PROTECTED]> wrote:
> Your instructions mention building DLLs. I'm not usi
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> Are there such beasts? I didn't know this is a Wine extension...
> But even if it is, one thing we can do is to integrate the
> bin2res into the build process. We can place the embedded data
> inside comments, and run bin2res before compiling an .rc
On Wed, 24 Sep 2003, Richard Cohen wrote:
> Provided you don't care about delay-loading libraries, you can already
> compile the programs with winegcc. Here's the patch
+$(MODULE).so: $(ALL_OBJS) $(RC_SRCS:.rc=.res) Makefile.in $(WINEWRAPPER)
+ $(RM) $(BASEMODULE)
+ $(WINEGCC) -m$(AP
On Wed, 24 Sep 2003, Steven Edwards wrote:
> Most of it should already build under Cygwin as cygwin1b apps. just
> $ ./configure && make tools && cd dlls && make
The difference is that I'm compiling Wine programs without Wine libraries,
let alone DLLs. Only a very limited set of libraries is com
Most of it should already build under Cygwin as cygwin1b apps. just
$ ./configure && make tools && cd dlls && make
You will have trouble with kernel32 and ntdll.
Also there is a patch to build Wineserver on cygwin floating around.
If you want to build apps that are linked to msvcrt.dll rather th
On Wed, 24 Sep 2003, Alexandre Julliard wrote:
> No, it's here so that you can compile with other resource compilers
> that don't support having binary data inline. It could be changed to
> #ifdef __WRC__ though.
Are there such beasts? I didn't know this is a Wine extension...
But even if it is,
"Dimitrie O. Paun" <[EMAIL PROTECTED]> writes:
> I'm not sure why we had those defines in there. In general, we try to avoid
> defines like the plague in the Wine tree, so your patch is much appreciated.
> It seems that was some code the initial developers had in there for their
> own testing, and
Pavel Roskin wrote:
I have looked at winegcc source and it seems it will greatly improve
portability. I think it's a good idea to switch to winegcc first.
Provided you don't care about delay-loading libraries, you can already
compile the programs with winegcc. Here's the patch
--
Richard
diff -u
On September 24, 2003 03:47 am, Pavel Roskin wrote:
> I have looked at winegcc source and it seems it will greatly improve
> portability. I think it's a good idea to switch to winegcc first.
>
> Thoose who compile large projects with Wine are not likely to abandon the
> Windows version, so it's he
On Wed, 24 Sep 2003, Dimitrie O. Paun wrote:
> On September 23, 2003 11:59 pm, Pavel Roskin wrote:
> > For example, winefile.exe needs "-luuid" in MinGW because it provides
> > IID_IDataObject. In Wine, IID_IDataObject is defined in
> > include/objidl.h and a constant number. Wine doesn't have u
On September 23, 2003 11:59 pm, Pavel Roskin wrote:
> For example, winefile.exe needs "-luuid" in MinGW because it provides
> IID_IDataObject. In Wine, IID_IDataObject is defined in include/objidl.h
> and a constant number. Wine doesn't have uuid library.
We have one, and it's called wine_uuid (
On Tue, 23 Sep 2003, Dimitrie O. Paun wrote:
> On September 23, 2003 11:02 pm, Pavel Roskin wrote:
> > The attached script makes it possible to compile many programs from Wine
> > under Windows. The only software needed on Windows is Cygwin with MinGW
> > libraries and some other utilities (flex,
On September 23, 2003 11:02 pm, Pavel Roskin wrote:
> The attached script makes it possible to compile many programs from Wine
> under Windows. The only software needed on Windows is Cygwin with MinGW
> libraries and some other utilities (flex, bison). Simply run setup.exe
> from www.cygwin.com a
Hello!
The attached script makes it possible to compile many programs from Wine
under Windows. The only software needed on Windows is Cygwin with MinGW
libraries and some other utilities (flex, bison). Simply run setup.exe
from www.cygwin.com and make sure to select MinGW development tools.
Then
35 matches
Mail list logo
