<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-2">
</head>
<body bgcolor="#ffffff" text="#000000">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 20px;" lang="x-central-euro">Hi,
<br>
<br>
I have two questions about the build system of WINE.
<br>
<br>
1.
<br>
<br>
Does WINE's build system deploy any kind of run-time CPU detection
while building the software?
<br>
<br>
I understand that a lot of things are configure by the configure
script; my question is that does this phase decide everything,
<br>
or are there further settings that are detected only during the
"make" phase?
<br>
<br>
(I am thinking of CPU-specific optimizations, done by GCC,
considering the CPU it's running on.)
<br>
<br>
I am asking this because I would like to build wine on a
completely different box than it is going to run on.
<br>
(The slow box1 is running a system mounted via NFS, and I can
chroot into the same directory on the fast box2, so the libraries
and compiler are the same in both environment, only the CPU is
different.)
<br>
<br>
Can I do this, or will this cause problems?
<br>
<br>
2.
<br>
<br>
If I successfully finish a build, and then later I modify some
random wine source files (or upgrade dependency libraries), and
restart "make" in the root directory, is the build system smart
enough to detect and rebuild only the parts that need rebuilding?
Or should I always do a make clean before that?
<br>
<br>
How about when I need to run the configure script again, because
some settings have changed? Do partial re-builds still work in
these cases?
<br>
<br>
Thank you for your help:
<br>
<br>
�� Kristof
<br>
<br>
</div>
</body>
</html>