Hans Leidekker hans@it.vu.nl writes:
-.res.res.cross.o: +.rc.res.cross.o: $(CROSSWINDRES) -i $< -o $@
Why do you need that? windres should work just fine with a .res file as input. What error do you get?
On Monday 19 April 2004 20:23, Alexandre Julliard wrote:
-.res.res.cross.o: +.rc.res.cross.o: $(CROSSWINDRES) -i $< -o $@
Why do you need that? windres should work just fine with a .res file as input. What error do you get?
'make crosstest' in dlls/user/test ends up wanting to build wrc which results in errors:
$ make crosstest gcc -g -O2 ../../../tools/wrc/wrc.c -o ../../../tools/wrc/wrc ../../../tools/wrc/wrc.c:22:20: config.h: No such file or directory ../../../tools/wrc/wrc.c:23:23: wine/port.h: No such file or directory In file included from ../../../tools/wrc/wrc.h:26, from ../../../tools/wrc/wrc.c:38: ../../../tools/wrc/wrctypes.h:25:20: windef.h: No such file or directory
[many more]
'make crosstest' would be more valuable if we didn't have to build all of Wine first and this is the only thing blocking that.
-Hans
On Monday 19 April 2004 04:23 pm, Hans Leidekker wrote:
'make crosstest' would be more valuable if we didn't have to build all of Wine first and this is the only thing blocking that.
This is possible to do without building all of wine, at the moment these are the steps I am running (after configure)
make -C libs make -C tools make crosstest
Hans Leidekker hans@it.vu.nl writes:
'make crosstest' in dlls/user/test ends up wanting to build wrc which results in errors:
$ make crosstest gcc -g -O2 ../../../tools/wrc/wrc.c -o ../../../tools/wrc/wrc ../../../tools/wrc/wrc.c:22:20: config.h: No such file or directory ../../../tools/wrc/wrc.c:23:23: wine/port.h: No such file or directory In file included from ../../../tools/wrc/wrc.h:26, from ../../../tools/wrc/wrc.c:38: ../../../tools/wrc/wrctypes.h:25:20: windef.h: No such file or directory
[many more]
'make crosstest' would be more valuable if we didn't have to build all of Wine first and this is the only thing blocking that.
Ah, I see. But actually you don't need to build all of Wine for crosstests, a simple 'make tools' should be enough.
On Monday 19 April 2004 23:28, Alexandre Julliard wrote:
'make crosstest' would be more valuable if we didn't have to build all of Wine first and this is the only thing blocking that.
Ah, I see. But actually you don't need to build all of Wine for crosstests, a simple 'make tools' should be enough.
Okay, I see you have put in a patch that makes the 'crosstest' target dependent on the 'tools' target (which depends on the 'libs' target).
Thanks.
-Hans