> Did you perhaps send me an old version of the tarball? The readme.txt
> for it was only 20 lines. The readme.txt you just sent the list is much
> more comprehensive and nicely answers my cookbook requests.
Uh, sorry, when you got the wrong one. The tarball should be okay, but I
exported it from (my) cvs, so maybe readme.txt wasn't updated.
> Here is the complete unix/Makefile in the tarball you sent me:
> PLDIR := ../../../..
> cp configure.ac $(PLDIR)
> cp wxwidgets.ac $(PLDIR)/cf
> cp drivers-init.ac $(PLDIR)/cf
> cp drivers-finish.ac $(PLDIR)/cf
> cp plDevs.h.in $(PLDIR)/include
> cp Makefile.am $(PLDIR)/drivers
> cp drivers.h $(PLDIR)/include
> cp plcore.h $(PLDIR)/include
> cp ../drivers/wxwidgets.cpp $(PLDIR)/drivers
> Obviously, you are copying back from the windows tree into the main tree
> which goes against our model of having the files in the main tree and
> copying to the windows subtree only if a pure windows build is required.
> (Note both cygwin and mingw work using just the normal Unix ./configure; make;
> make install sequence.)
Oh, that's just temporary. I didn't want to fiddle around with the
source code in the first place until I understood the plplot source code
more. In the second place I never worked with configure and automake and
so on. And I had full control about which files I changed.
This makefiles just copies files back into the normal source tree and
overwrites these files. Than run cf/bootstrap.sh and all is as it should
Since as said I never have worked with configure before, it would maybe
wise someone checks that. If it's okay, I make a patch as you explained
below and everything goes it's ways as it should.
> Would you please switch to our model of doing things? That will of course
> require added files and modified files in the main tree, but the way you
> should send those to me is as a patch.
No problem at all.
> Here is how you should produce a patch on the Linux system that is
> accessible to you.
> unpack 5.5.3 tarball which creates a tree with the top-level directory =
> cp -a plplot-5.5.3 plplot-5.5.3new
> copy the above files into the correct location in plplot-5.5.3new
> overwriting some of the files and adding new files in some cases. To keep
> things simple for now, lets exclude any changes in sys/win32, but of course
> those can be added in later if I get the Linux version (with files in the
> requested positions) to work.
> You should not compile anything in either plplot-5.5.3 or plplot-5.5.3new.
> That is, both should be clean directory trees. However, you could do the
> following to make sure everything is in the correct position in
> cp -a plplot-5.5.3new plplot-5.5.3_working
> cd plplot-5.5.3_working
> ./configure --enable-wxwidgets, etc.
> To produce the requested patch from the two clean directory trees set up
> above do the following:
> diff -Naur plplot-5.5.3 plplot-5.5.3new >plplot-5.5.3.patch
> Please review plplot-5.5.3.patch to make sure those are the exact changes to
> the main tree that you require and nothing extra. Afterwards do the
> gzip plplot-5.5.3.patch
> Send plplot-5.5.3.patch.gz (the file created by gzip) to me.
I'll do that tomorrow morning (Europe time).
> When I apply that patch to 5.5.3, then I should be able to ./configure
> --enable-wxwidgets immediately, and do make && make install without copying
> any files assuming I have understood your directions properly. Although, I
> can only test on Linux, note this ./configure method with the above files in
> the correct locations has the potential (assuming the correct libraries are
> installed) to work on OS X, cygwin, and mingw without requiring the copying
> of any files.
Hm, sadly at least it doesn't work on OS X right now :(
> The pure windows version in sys/win32 will require some
> additional copying of files from the main tree, but we can deal with that
> issue later after verifying the Linux version with files in the correct
> position works.
> BTW, I am sending this e-mail also directly to you to see whether
> that e-mail route works again.
Hm, you could also use wsmekal@... to send me emails directly.