Boehm GCを弄ってみる - 匣の向こう側

yaneSDK4Cppを作るとしたら、C++にGCがないのでyaneSDK4D/Csとは結構違いがでそうという話が出てた。で、C++で使えるGCとしてBoehm GCがあったので、興味本位で弄ってみた。

Boehm GCはこちらから入手。

A garbage collector for C and C++
http://www.hpl.hp.com/personal/Hans_Boehm/gc/

また、使い方の説明はこちらが分かりやすいです。

Boehm GC を使ってみる
http://www.namikilab.tuat.ac.jp/~sasada/prog/boehmgc.html

GCがあると楽だと思いますが、結局のところUnmanagedリソースの解放が難しくなる気がします。メモリだけで済むオブジェクトはGCを使いUnmanagedリソースを扱うオブジェクトはshared_ptrと言うように、合わせ技でやるというのもあるかも知れませんが、これはこれで混乱しそう。
なにか上手い方法はないかしら・・・

あと、Boehm GCをVisual C++.NETでmakeしようとするとエラーが出ます。
付属のNT_Makefileをちょっと修正すれば良いのですが、忘れそうなのでここでメモっておこう(^^;
あ、タブをスペース4つに置き換えています。

# Makefile for Windows NT.  Assumes Microsoft compiler, and a single thread.
# DLLs are included in the root set under NT, but not under win32S.
# Use "nmake nodebug=1 all" for optimized versions of library, gctest and editor.

CPU= i386
!include 

OBJS= alloc.obj reclaim.obj allchblk.obj misc.obj mach_dep.obj os_dep.obj \
      mark_rts.obj headers.obj mark.obj obj_map.obj blacklst.obj finalize.obj \
      new_hblk.obj dbg_mlc.obj malloc.obj stubborn.obj dyn_load.obj typd_mlc.obj \
      ptr_chck.obj gc_cpp.obj mallocx.obj

all: gctest.exe cord\de.exe test_cpp.exe

.c.obj:
    $(cc) $(cdebug) $(cflags) $(cvars) -Iinclude -DSILENT -DALL_INTERIOR_POINTERS \
    -D__STDC__ -DGC_NOT_DLL $*.c /Fo$*.obj

.cpp.obj:
    $(cc) $(cdebug) $(cflags) $(cvars) -Iinclude -DSILENT -DALL_INTERIOR_POINTERS \
    -DGC_NOT_DLL $*.CPP /Fo$*.obj

$(OBJS) tests\test.obj: include\private\gc_priv.h include\private\gc_hdrs.h \
    include\gc.h include\private\gcconfig.h include\private\gc_locks.h \
    include\private\gc_pmark.h include\gc_mark.h

gc.lib: $(OBJS)
    lib /MACHINE:i386 /out:gc.lib $(OBJS)
# The original NT SDK used lib32 instead of lib

gctest.exe: tests\test.obj gc.lib
#    The following works for win32 debugging.  For win32s debugging use debugtype:coff
#    and add mapsympe line.
#  This produces a "GUI" applications that opens no windows and writes to the log file
#  "gc.log".  This is done to make the result runnable under win32s.
    $(link) -debug:full -debugtype:cv $(guiflags) -stack:131072 -out:$*.exe \
    tests\test.obj $(guilibs) gc.lib
#    mapsympe -n -o gctest.sym gctest.exe

cord\de_win.rbj: cord\de_win.res
    cvtres /machine:X86 /out:cord\de_win.rbj \cord\de_win.res 

cord\de.obj cord\de_win.obj: include\cord.h include\private\cord_pos.h \
    cord\de_win.h cord\de_cmds.h

cord\de_win.res: cord\de_win.rc cord\de_win.h cord\de_cmds.h
    $(rc) $(rcvars) -r -fo cord\de_win.res cord\de_win.rc

# Cord/de is a real win32 gui application.
cord\de.exe: cord\cordbscs.obj cord\cordxtra.obj cord\de.obj cord\de_win.obj \
    cord\de_win.rbj gc.lib
    $(link) -debug:full -debugtype:cv $(guiflags) -stack:16384 -out:cord\de.exe  \
    cord\cordbscs.obj cord\cordxtra.obj cord\de.obj cord\de_win.obj \
    cord\de_win.rbj gc.lib $(guilibs)

gc_cpp.obj: include\gc_cpp.h include\gc.h

gc_cpp.cpp: gc_cpp.cc
    copy gc_cpp.cc gc_cpp.cpp

test_cpp.cpp: tests\test_cpp.cc
    copy tests\test_cpp.cc test_cpp.cpp

# This generates the C++ test executable.  The executable expects
# a single numeric argument, which is the number of iterations.
# The output appears in the file "gc.log".
test_cpp.exe: test_cpp.obj include\gc_cpp.h include\gc.h gc.lib
    $(link) -debug:full -debugtype:cv $(guiflags) -stack:16384 \
    -out:test_cpp.exe test_cpp.obj gc.lib $(guilibs)