> On Jul 1, 5:25 pm, "Ryan Sleevi" <[email protected]> wrote:
> > Sorry, I should have reviewed what I sent :)
> >
> > As of 4.0, Enblend/Enfuse transitioned to a CMake build system. So
> the
> > patches should no longer be necessary, you should be able to just
> CMake it.
> >
> I'm stuck. I thought that MSVC would include all the necessary STL
> headers, so I left out StlPort in my first attempt. I was missing
> <slist>, the non-standard single-linked list. I tried substituting
> <list>, but mask.h uses slist::insert_after, which is unique to slist,
> used for better performance.
> 
> So I backed up and tried to include StlPort, but it doesn't configure
> for msvc10, and if I configure for msvc9, it won't 'nmake':
> nmake clean install
> ....stlport\stl/_cstdlib.h(158) : error C2084: function '__int64
> abs(__int64)' already has a body
> .....
> conflict with MSVC headers
> 
> Boost has an 'intrusive' slist, which would require deriving the
> contained class from a boost hook class. Good idea?
> Better ideas?
> 

Have you checked to see if the issue has already been addressed by STLport?
A quick Google turns up
http://sourceforge.net/projects/stlport/forums/forum/490892/topic/3695497 in
the number one result for "stlport visual studio 2010". At result #3,
http://www.lenholgate.com/archives/000905.html shows up (although, to be
fair, it looks like that was just posted today). I'd check to see if you
can't work it out with those two.

Historically, STLport has had much better performance characteristics than
the MSVC STL (which itself is licensed from Dinkumware, IIRC). This is one
of the reasons why it is part of the build steps. Was there a reason you
were explicitly trying to avoid STLport?

-- 
You received this message because you are subscribed to the Google Groups 
"hugin and other free panoramic software" group.
A list of frequently asked questions is available at: 
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx

Reply via email to