Dave Akers (dla)
Mon, 27 Mar 2000 11:25:50 -0800
Correct you are.. As for the header file, the problems you encountered
have to do with assignment of streams. The ostream_withassign class under
the MIPSPro compiler allows copying of streams, while the same class is
called "_IO_ostream_withassign" under g++.. Brilliant, isn't it? ;)
Anyway, providing a version of Volumizer 1.2 built under g++ wouldn't be
too much work, but there are a few issues. Out of curiosity, can I ask why
you want to be able to work with g++ on your SGI boxes?
Thanks,
Dave
On Fri, 24 Mar 2000, Sean Spicer wrote:
>
> Okay...so I'm kinda answering my own question. Grin.
>
> I should have recognized this earlier, but one cannot build Volumizer apps
> with g++. Why? Well, it has to do with a nifty little feature of C++
> called name mangling.
>
> In a nutshell, even if the Volumizer headers in 1.2 were g++ complient
> (which they are not in the current release), any code you might build
> would not be able to link to the appropriate symbole in libvo.so. This is
> because libvo.so was compiled (and had it's names mangled by) a MipsPro
> compiler. Your code compiled under g++ would have names mangled using the
> g++ style. Unfortunately the MipsPro and GNU styles are not
> compatible. So this is not going to work unless SGI provides a GNU built
> version of libvo.so.
>
> So my other question is moot.
>
> I hope this helps everyone. grin.
>
> sean
>
> ___________________________________________________________________________
> Sean Spicer Stanford University Medical Center
> Biomechanical Engineering Division of Vascular Surgery, Suite H3642
> Cardiovascular Biomechanics Lab Stanford CA, 94305
> Telephone...650.723.1695
> Fax.........650.723.8762
>
> http://solvedeath.stanford.edu/~spicer
>
>
>
This archive was generated by hypermail 2.0b2 on Mon Mar 27 2000 - 13:20:05 PST