From: Grzegorz J. <ja...@he...> - 2003-03-10 02:31:26
|
On Fri, 7 Mar 2003, Michael Hohmuth wrote: > Grzegorz Jakacki <ja...@he...> writes: > > > Thank you very much for your contribution. The gcc-3.x compatibility issue > > surfaces regularily. Recently Alexandre Tolmos has merged the old patch > > prepared by Michael Buro addressing exactly this same problem, and is > > currently in the phase of testing it on Compile Farm. > > > > This unfortunately means, that some work has been done twice. [...] > > Next time, I would suggest that you first contact the mailing list or me > > directly to discuss the contribution you would like to make. The project > > resources are scarce and I would hate to waste time of any contributor. > > > > I am not sure if you are subscribing to the OpenC++ mailing list, since > > gcc-3.x patch was discussed here. > > [...] archived at [sourceforge.net] since Sep 2002. > > I am, in fact, subscribed to the list (and I even have a complete > mailing-list archive dating back to May 1997), Could you make a tarball out of it and send it to me? I think we should put it on the website. I have been trying to find the complete archive for several times, but I failed. > but I have not followed > it closely during the few past months. Now it turns out I should have > (but then again, it wasn't that much work). > > > Nevertheless, it would be reasonable to try to merge your changes after > > Alexandre is done, so that we are sure that no detail has been lost. If > > you feel comfortable with CVS merge facilities I would encourage you to > > merge yourself (send me your SF userid for CVS access). This however may > > be tedious, so if you do not volunteer to do this part, I can do it. > > I'd be happy to do the merge. Great. > My SF ID is "rotofoil". You have been added to the project. Currently Alexandre Tolmos is finishing his commits wrt. gcc-3.x, there will be an annoucement once he is done. Before this happens you may want to contact me if you think you need any help on branching/merging. [...] > I do not have any experience with SF's compile farm and could use some > help in testing. Unfortunately, I do not have the time to manually > configure and test OpenC++ on each and every architecture and > compiler. Is there an automated way to try a compilation on all > architectures? This is what I would love to have. I am working on a script, that would just configure, build, compile and test on a given platform, possibly sending the results in e-mail. There is a problem with making a script for all the platforms, because of strange login procedure at CompileFarm, but this eventually can be solved too. The testing on CF has been simplified thanks to adoption of sandbox branches methodology. You keep all your changes in your branch, (e.g. sandbox_rotofoil), which you merge into main trunk after you test them. This simplifies testing on remote hosts (on CF), because in fact the only thing you need to supply is the name of sandbox to test. This is how it looks today: (1) log on and select host (2) checkout files from 'sandbox_rotofoil' (3) cd opencxx; ./configure; make test This is how I hope it is going to look in one-month timeframe: (1) log on and select host (2) ./build-and-test --tag=sandbox_rotofoil This is what I would love to have (1) ./multihost-build-and-test --tag=sandbox_rotofoil > Which architectures need to be considered as ``supported by OpenC++''? Currently we have resources to support i86/Linux, Sun/Linux and Sun/Solaris, hopefully we will be supporting MacOS X is the near future. (I think the head revision still compiles on i86/Cygwin and HPUX, but I have no way of verifying it.) Feel free to contact me if you have any questions. Best regards Grzegorz ################################################################## # Grzegorz Jakacki Huada Electronic Design # # Senior Engineer, CAD Dept. 1 Gaojiayuan, Chaoyang # # tel. +86-10-64365577 x2074 Beijing 100015, China # # Copyright (C) 2002 Grzegorz Jakacki, HED. All Rights Reserved. # ################################################################## |