Hans-Christoph Steiner wrote:
On Oct 19, 2006, at 4:43 AM, IOhannes m zmoelnig wrote:
Hans-Christoph Steiner wrote:
I am getting conflicts just my using your build stuff. Could you remove zexyconf.h from CVS since its dynamically generated? Otherwise this will require manual intervention after automatic builds. RCS file: /cvsroot/pure-data/externals/zexy/src/zexyconf.h,v retrieving revision 1.3 retrieving revision 1.4 Merging differences between 1.3 and 1.4 into zexyconf.h rcsmerge: warning: conflicts during merge cvs update: conflicts found in zexy/src/zexyconf.h C zexy/src/zexyconf.h
i see. this is indeed a problem. the reason why zexyconf.h is checked in, is that you can also build zexy with M$VC without running configure first: in this case nobody will create the zexyconf.h file, which - imho - makes building overcomplicated (i don't think it is an option to tell people to copy zexyconf.h.in to zexyconf.h and edit to their needs).
That sounds good. I think its far too much work to support every compiler under the sun. I like gcc on all platforms.
Yes black and white is easier than colour. But if MS has made the OS then MS 's compiler is likely to be the best for that platform. There are only three (3) platforms that anyone here has ever mentioned. gcc is really good on linux. Martin