Hi
I do not know why you are having trouble. Others have built SC with vs08 and vs10 and haven't had that issue.
Have you made any changes to the code? If so, try to build using the original files and see if the problem persists.
It looks like you sent 3 almost identical messages to the list. I didn't realize how similar they were until after I'd approved 2 of them.
Messages from new list members are delayed until I look at them to discourage spam, and that's why your first message didn't go through immediately.
Regards
Mark
--
You received this message because you are subscribed to the Google Groups "STEPcode - Developers Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scl-dev+u...@googlegroups.com.
To post to this group, send email to scl...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scl-dev/3f06eee8-175e-4754-a4cc-81d3644bc2a8%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Davy,
Thank you for taking a look.
Wangdong,
One of the errors was discussed at https://github.com/stepcode/stepcode/issues/273 . I meant to work on it, but have not had a chance to do so.
Regards
Mark
To view this discussion on the web visit https://groups.google.com/d/msgid/scl-dev/71014E2C48AC473194A8EC38839C3E86%40pcdual.
@Mark,It seems that this commit (https://github.com/stepcode/stepcode/commit/b5af88b26809037348e609514e48d98248524268) introduces the linker problem in MSVC 2010.After some more looking through the code I remembered I fixed a similar issue in the past with error descriptors where we needed to prevent std::string instances to be exportedfor msvc2010 because ::npos member did not get imported by a .exe.This was logged as a bug in msvc2010 first, but then closed as 'by design', meaning just don't export stl stuff :(msvc 2005 and 2008 did not have this problem, I don't know about newer versions than 2010.Did this commit have more reasons other than fixing warnings?
Regards,Dave