On Tue, 27 Jun 2000, Eric Pouech wrote:
> "Wilbur N. Dale" wrote:
> >
> > 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.
[snip]
> why don't you just use a separate directory where to store the shared files
> (among your 4 examples) and use relative paths in your makefile ?
Thanks, I had not thought of that, but someone (not on the wine lists) has told
me a better way for my purpose. Since this is an example people will be staring
at, I want the code in the directory where they can easily see it with all of
the related code and it will look more like how they will port their code.
The altenate solution suggested to me is to make the shared files "generated
source" that is generated by the symbolic link command. Now the user types
./configure
make
and the symbolic links are generated during the compile.
make distclean
will also remove the symbolic links.
So far I have 3 out of 4 cases converted.
>
> A+
> --
> ---------------
> Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
> "The future will be better tomorrow", Vice President Dan Quayle
--
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
