bcd.gen: Help wanted with Windows porting
Bradley Smith
digitalmars-com at baysmith.com
Fri Aug 4 17:47:45 PDT 2006
I don't have an accurate way of measuring the memory used, but it
appears to use about 70-80 M.
Bradley
Gregor Richards wrote:
> Hmmmmmmmmmmmmmmm.
>
> I doubt that the results are wrong, but I'll bet the memory usage is on
> the bad end of the scale ... do you have a way to test how much memory
> it uses in a run?
>
> - Gregor Richards
>
> Bradley Smith wrote:
>> I made an attempt to build bcd.gen on Windows. Here are my notes.
>>
>> 1. The libxml2-2.4.12 at gnuwin32.sourceforge.net appears to be
>> missing xmlReadFile. Instead, used libxml2-2.6.26.win32.zip from
>> http://www.zlatkovic.com/pub/libxml/.
>>
>> 2. Converted libxml2.dll to libxml2.lib using implib.exe from
>> DigitalMars. Conversion of lib\libxml2.lib using coeff2omf.exe didn't
>> work because undefined symbols remained.
>>
>> 3. Crashes occur when calling free() on char* returned from libxml2.
>> Tried converting free() calls to xmlFree(), but crashes still occured.
>> Subsituting a noop stup for xmlFree() allows bcdgen to run without
>> error, but I can't confirm the result is correct. This problem with
>> calling free() may be a consequence of linking to the libxml2.dll via
>> implib.exe
>>
>>
>> Bradley
>>
>>
>>
>> Gregor Richards wrote:
>>
>>> As far as I know, there is nothing platform-specific about bcd.gen,
>>> but I have no means of porting it to Windows.
>>>
>>> So, I need somebody who's fairly good at typing 'make', and perhaps
>>> even editing your path, to see if you can get bcd.gen to compile and
>>> function on Windows.
>>>
>>> Its two prerequisites are both available in binary form:
>>>
>>> gccxml:
>>> http://prdownloads.sourceforge.net/ctypes/gccxml-20050318-setup.exe?download
>>> (I hope this is recent enough ...)
>>>
>>> libxml2: http://gnuwin32.sourceforge.net/packages/libxml2.htm
>>>
>>> Other than that, you should just need 'make'. Any help
>>> porting/testing would be greatly appreciated. Please respond either
>>> via email or to the newsgroup.
>>>
>>> - Gregor Richards
More information about the Digitalmars-d
mailing list