winetest: move to resources
Ferenc Wagner
wferi at afavant.elte.hu
Tue May 4 16:58:49 CDT 2004
Alexandre Julliard <julliard at winehq.org> writes:
> Ferenc Wagner <wferi at afavant.elte.hu> writes:
>
>> My first implementation did exactly that. However, these
>> pieces of information have their places in the depencency
>> tree and I managed to screw up my build more often than not
>> without the help of make. Beyond that, moving this little
>> complexity out of the Makefile leads to much more complexity
>> in a couple of other places. I did my best not to bother
>> uninterested parties by these small files; I think they
>> would go unnoticed. Are you still holding your position?
>>
>> Btw the real solution to the ugliness would be the use of
>> the .DELETE_ON_ERROR special target, isn't that portable?
>
> No, it's not, and frankly I don't see why you would need that.
> Could you please explain a bit more what you are trying to do?
Oh, that was a real 'btw' side note; I meant the usual
... || ( $(RM) $@ && exit 1 ) stanzas, which we have to keep
repeating all to often. I skimmed through the compatibility
section in the make manual but found no portability issues
with respect to this special target. An overlook, probably.
Back to the topic: my main point is that the situation is
best expressed by a Makefile and solved by make. Best as
opposed to verbosity and complexity. I suppose this is also
a fairly workable scheme for those who build the winetest
packages while being transparent for others. And still a
very straightforward application of make. I can't really
see sane way to do all of this in maketest without
triggering superfluous relinks all the time; maybe I miss
something obvious.
--
Feri.
More information about the wine-devel
mailing list