From: Jeremy C. <jer...@gm...> - 2008-01-03 21:19:41
|
On Jan 3, 2008 11:45 AM, Josh Cherry <jc...@nc...> wrote: > > > On Thu, 3 Jan 2008, Jeremy Conlin wrote: > > > I double checked and I do have the copy constructor defined and the file > > where it is defined (Material.cpp) is used during the installation. > What > > gives? > > I can't say. Usually you would compile that to Material.o and link > against it. Either you're not linking against Material.o or it lacks that > symbol. Another tool that can help you figure this out is nm. See also > http://www.dabeaz.com/cgi-bin/wiki.pl?SwigFaqCPlusPlusUnresolvedSymbols. > The tool I use for compiling/linking/installing is Python's distutils. This *should* work the same on different platforms. This problem baffles me. Jeremy |