Hello,
I finished the example code for DLLs this week end and I am ready to submit a
patch. However, before I submit the patch, I want to make sure I do not screw
up CVS by using symbolic links in the source tree. I do not use CVS since my
intention is to only change HOWTO-winelib, but I have read up on it recently.
However, I did not see any reference to symbolic links in the documentation.
The code consists of four examples with each example in its own directory. Among
the examples, there are binary files (*.dll, *.exe), header files (*.h), and
source files (*.c) that I want to keep in sync (always identical). If a header
file is the same as in another example, I use a symbolic link with a relative
path.
As I understand it, if I later change the header file, CVS will create an
incorrect patch file since it will "see" two files change: the original file
and the symbolic link. Applying the patch will cause the the same diffs to be
applied twice to the file: once to the file and once through the symbolic
link.
Does CVS provide a way to handle this? Or is there a better way do share files
than symbolic links?
I am aware of the CVS issue with binary files and I will re-RTFM and handle
that before I submit the patch.
Also, if anyone needs these examples immediately, I will be glad to send you
the current version via email. They work with the 20000614 version of wine. I
see Alexandre Julliard changed the name of tools/build to tools/winebuild in
the current CVS so you need to make some changes to get it to work in the
current CVS.
--
Wilbur Dale
Lumin Software BV
Zandheuvel 52 B
4901 HW Oosterhout (NB)
The Netherlands
phone: +31-(0)162-47.88.42
fax: +31-(0)162-43.31.52
