Re: [Raypp-general] Makefile

[Andreas K. <and...@we...>]

Hi all!

> I think a reasonable compromise would be to build multiple translation units 
> in the CVS, but possibly release tarballs with the fast compile switched on. 
> Any thoughts?

I personally prefer a single simple solution, since it much easier to maintain.
Adding a file to the ray++.cxx is easier than modifying the Makefile 
especially if you work on Windows where you cannot test if the Makefile
works. 
Side note: the MSVC++60 workspace already has two projects for the 
ray++ library, one using ray++.cxx and one compling the file individually.
It's out of date, new file were not added there...

What I do to avoid long compile times for new stuff: I do not add new files
to ray++.cxx directly but add the new file to the project/Makefile. Before
I submit it CVS I add it to the ray++.cxx.

> > > Could you please upload it as a sourceforge patch first?
> > 
> > I didn't know this was possible. I'll have to tidy up the makefile a bit and 
> > investigate how to achieve building a sourceforge patch.
> 
> I'm not sure how it works, but Andreas has done it already for his flexible
> sampling class. But sending the modified files to the mailing list is
> also fine, of course.

Not very hard. Create a patch the usual way (using diff against the CVS 
version) and save it ti a file. On our sorceforge page, go to "Patches"
and "Submit new". Attach the patch file you created.

Andreas