From: Arthur N. <ac...@ca...> - 2025-03-29 08:51:45
|
Another thought if the build files etc in the csl/new-embedded directory are not in step with the current main version of the trunk is that you can easily go svn -r NNN update on the whole tree to go backwards in time until you find a version that works for you. If I browse the sources on sourceforge I find that for revision 6789 a checkin has the message "Web REDUCE Makefile" so around then might be a good place to start. For experiments at the stage you are at thus far working with a version that does not include the last year of various updates would not be a huge issue.... and if you make good enough progress with that to feel that the project as a whole is going to work then (a) it will provide us with a strong incentive to bring that area up to date (b) the delay will mean that maybe some of us will be under less pressure from other directions and (c) you will have built up your Reduce skills and experience! I do not guarantee that revision 6788 or 6789 is a good one! In cases like this I go sort of way back and then do a binary chop on revision numbers to find where key changes were made - and then I can often see just what they were and allow for them. That tends to be a bit tedious and I ususlly make a script that goes basically svn -r $1 update [sometimes I need to tidy up or delete built files here] [sometimes I need to re-run a "configure" script] make and have a picxe of paper where I keep score for how various revisions behave... Good luck. Arthur |