Compiling with VC++ 6.0
-
- Star Pilot
- Posts: 7
- Joined: Sun Nov 09, 2003 7:20 pm
- Location: Kiev, Ukraine
Compiling with VC++ 6.0
Well, I've tried compiling the CVS source using Microsuxx Visual C++ 6.0, I know that was a bad idea . So after removing LOTS of minor strange "errors", for example: for some reasons it didn't like "cout<<(something)<<endl;" so I've replaced it with "\n", linker gave me a list of apr. 260 "unresolved external symbols". Like that one:
"unit_wrapper.obj : error LNK2001: unresolved external symbol "class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> > __cdecl UniverseUtil::getSubVariable(class _STL::basic_string<char,class _STL::char_traits<char>,
class _STL::allocator<char> >,class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> >,class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> >,class _STL::basic_string<char,class _ST
L::char_traits<char>,class _STL::allocator<char> >)" (?getSubVariable@UniverseUtil@@YA?AV?$basic_string@DV?$char_traits@D@_STL@@V?$allocator@D@2@@_STL@@V23@000@Z)"
Dont you think it's A BIT strange?
And why is it blaming STL for all of this?
"unit_wrapper.obj : error LNK2001: unresolved external symbol "class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> > __cdecl UniverseUtil::getSubVariable(class _STL::basic_string<char,class _STL::char_traits<char>,
class _STL::allocator<char> >,class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> >,class _STL::basic_string<char,class _STL::char_traits<char>,class _STL::allocator<char> >,class _STL::basic_string<char,class _ST
L::char_traits<char>,class _STL::allocator<char> >)" (?getSubVariable@UniverseUtil@@YA?AV?$basic_string@DV?$char_traits@D@_STL@@V?$allocator@D@2@@_STL@@V23@000@Z)"
Dont you think it's A BIT strange?
And why is it blaming STL for all of this?
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
What types of errors are these?
Try opening up the networking folder on ProjectView and right click on the lowlevel folder and click "Add files to folder" and browse to vegastrike\src\networking\lowlevel. (you probably have to click up one level). Select all of the files.
see if that fixes any errors
Also, I hate to say it, but if you start getting a lot of wierd errors after making a few changes, try a rebuild all.
Try opening up the networking folder on ProjectView and right click on the lowlevel folder and click "Add files to folder" and browse to vegastrike\src\networking\lowlevel. (you probably have to click up one level). Select all of the files.
see if that fixes any errors
Also, I hate to say it, but if you start getting a lot of wierd errors after making a few changes, try a rebuild all.
-
- Star Pilot
- Posts: 7
- Joined: Sun Nov 09, 2003 7:20 pm
- Location: Kiev, Ukraine
The errors during the compiling process were connected with "endl" object, the compiler didn't like it for some reasons, other said something about missing classes (in network modules), but including the headers directly into the cpp solved the problem, then there were some more strange errors connected with "iostream.h" that led to errors in other standart headers. And during the linking, the first of them said that "LIBC" library is conflicting with others, so I placed it to the ignore list.
I added all the files from network\lowlevel folder, but still lots of errors. I think that the problem is in IDE(Visual C++) or some libraries, that are linking with the project, for example - the new STLport, that I use instead of standart Microsoft STL. Well rebuilding the whole project is a radical thing indeed. But the next thing (after rebuilding) I'll try compiling it directly using command line, maybe that will help. Thanks anyway!
I added all the files from network\lowlevel folder, but still lots of errors. I think that the problem is in IDE(Visual C++) or some libraries, that are linking with the project, for example - the new STLport, that I use instead of standart Microsoft STL. Well rebuilding the whole project is a radical thing indeed. But the next thing (after rebuilding) I'll try compiling it directly using command line, maybe that will help. Thanks anyway!
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
-
- Developer
- Posts: 427
- Joined: Thu Jan 09, 2003 6:03 am
-
- Elite
- Posts: 1454
- Joined: Sun Jan 12, 2003 6:24 pm
- Location: Far out in the uncharted backwaters of the unfashionable end of the western spiral arm of the Galaxy
- Contact:
-
- Merchant
- Posts: 36
- Joined: Mon Jan 19, 2004 5:07 pm
- Location: fr
version 0.3.9 ?
2 days ago, I checked out the /vegastrike/vegastrike and /vegastrike/vega-proj modules.
I added the /lowlevel missing files (thx ace123) into the project and got the whole compiled with VC6 (I thought it would be harder). But the generated exe was 0.3.9.0, as stated in the /vegastrike/resources.rc file.
Here is my question: which version am I really compiling ? 0.3.9 ? or is the resources.rc not up to date ?
I added the /lowlevel missing files (thx ace123) into the project and got the whole compiled with VC6 (I thought it would be harder). But the generated exe was 0.3.9.0, as stated in the /vegastrike/resources.rc file.
Here is my question: which version am I really compiling ? 0.3.9 ? or is the resources.rc not up to date ?
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact: