<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I guess Unicode_WIDECHAR = TRUE is what you picked, so:<BR> <BR>if not defined("Unicode_WIDECHAR")<BR> Unicode_WIDECHAR = FALSE<BR>end<BR>in cm3cfg.common and libunicode/src/m3makefile<BR> <BR>and then if Unicode_WIDECHAR around the rest of libunicode/src/m3makefile?<BR> <BR> <BR>I would have likely used a function returning byte size.<BR> <BR> <BR> <BR> - Jay<br><br> <BR><div><hr id="stopSpelling">From: jay.krell@cornell.edu<br>To: rcolebur@scires.com; m3devel@elegosoft.com<br>Subject: RE: [M3devel] build problems with libunicode<br>Date: Fri, 30 May 2014 00:07:11 +0000<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Can <a href="https://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/libunicode/src/m3makefile" target="_blank">https://dcvs.elegosoft.com/cgi-bin/cvsweb.cgi/cm3/m3-libs/libunicode/src/m3makefile</a><br> <br> <br>do something to filter itself out from building with a compiler that won't work?<br> <br>Can you add a builtin quake function<br>WideCharByteSize() or some other name<br> <br>that returns 2 or 4, and in cm3cfg.common, if it isn't already defined (builtin), define one that returns 2?<br>and then, in libunicode/src/m3makefile, do the same thing, define a function that returns 2 if it isn't already defined?<br> <br> <br> <br> - Jay<br><br><br><div>> From: rcolebur@SCIRES.COM<br>> To: m3devel@elegosoft.com<br>> Date: Thu, 29 May 2014 21:37:59 +0000<br>> Subject: Re: [M3devel] build problems with libunicode<br>> <br>> Rodney:<br>> <br>> I looked thru the various cm3.cfg files (and the ones that get included) and I don't anywhere see a line with "Unicode_WIDECHAR" in it.<br>> <br>> So, not sure why libunicode is trying to build on Windows (NT386).<br>> <br>> --Randy Coleburn<br>> <br>> -----Original Message-----<br>> From: Coleburn, Randy <br>> Sent: Thursday, May 29, 2014 4:55 PM<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] build problems with libunicode<br>> <br>> Rodney:<br>> <br>> Thanks very much for your response.<br>> <br>> As far as I know, I've not changed the default configuration of my compiler, so based on your statement, I don't see why libunicode should be trying to build.<br>> <br>> I'll take a look at your release notes.<br>> <br>> Thanks,<br>> Randy Coleburn<br>> <br>> -----Original Message-----<br>> From: Rodney M. Bates [mailto:rodney_bates@lcwb.coop] <br>> Sent: Thursday, May 29, 2014 11:27 AM<br>> To: m3devel@elegosoft.com<br>> Subject: EXT:Re: [M3devel] build problems with libunicode<br>> <br>> <br>> <br>> On 05/29/2014 12:40 AM, Coleburn, Randy wrote:<br>> > I've been rebuilding everything from the HEAD branch on Windows XP (32-bit).<br>> ><br>> > The m3-libs\libunicode package fails to build (see errors below).<br>> ><br>> > I haven't taken time yet to look at the source code, but wanted to go ahead and post these results to the group in case someone knows of a quick fix.<br>> ><br>> > The problem module is: UnsafeUniCodec.m3<br>> ><br>> > Thanks,<br>> ><br>> > Randy Coleburn<br>> ><br>> <br>> I am responsible for libunicode.<br>> <br>> 1. libunicode won't and is not designed to build unless the compiler is<br>> configured to make WIDECHAR have full unicode range, which, by default,<br>> it is not.<br>> <br>> 2. The simplest way to thus configure the compiler is to add the line<br>> Unicode_WIDECHAR="TRUE" to cm3.cfg, in /usr/local/cm3/bin, then rebuild<br>> everything, starting with m3core.<br>> <br>> You can bootstrap all of this using the release compiler, see cm3/scripts/README-build-unicode<br>> <br>> I put libunicode in a separate package for that reason, and left the compiler configured by default for the existing 16-bit range of WIDECHAR, so there would be no perturbation to anybody's code unless you take some action.<br>> <br>> We can change the default if there is consensus to do so. Most code should not be affected, but some lower-level things will be. There is lots of info on this subject, including what you get from it and what kinds of code might be affected in:<br>> <br>> cm3/README-unicode-summary<br>> cm3/README-unicode<br>> cm3/scripts/README-build-unicode<br>> <br>> Rodney Bates<br>> rodney.m.bates@acm.org<br></div> </div></div> </div></body>
</html>