Dave Puchyr wrote: > I was able to build embedded versions of 0.5.0b1 with the c++ > compilers and configurations detailed below.
What is the point of this? I mean, by don't you build Cherokee with a C compiler and your handler with C++. As far as you get a dynamic library with the needed symbols, it should work. > The diffs to make the builds work are also below. The diffs aren't > ready for prime time but do produce working servers, albeit > minimally tested. I have been applying some of those change for an hour or some. Some of them are non-senses for me: castings over previous castings, castings to its type, etc. > The bulk of the diffs deal with replacing the variable/data members > names "new", "template", "true", and "false", which are all reserved > words in c++, and explicitly casting pointers. Are "false" and "true" a problem for the C++ compiler? Could we add a conditional define to typedef cherokee_boolean_t to the C++ bool? > Alo, I'll send you the diffs as an attachment. Sweet! Thanks Dave PS: I'm committing some of your changes now. -- Greetings, alo. http://www.alobbs.com _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
