imbehindu656 / darkbasicpro

Automatically exported from code.google.com/p/darkbasicpro
0 stars 0 forks source link

DarkBasicProSolution.sln has compile/linker erorrs #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Check out the source code (read-only)
2. Click DarkBasicProSolution.sln to open it up
3. Build the solution.

What is the expected output? What do you see instead?
A. Almost every project has the following linker warning:
warning LNK4075: ignoring '/EDITANDCONTINUE' due to '/INCREMENTAL:NO' 
specification

B. Four projects have errors.
1. ConvMD3: d3dx9dt.lib not found. To correct this, remove d3dx9dt.lib from the 
project's dependencies. It's been discontinue from DirectX, and was not used in 
the code.

2: ConvX: d3dx9dt.lib not found. To correct this, remove d3dx9dt.lib from the 
project's dependencies. It's been discontinue from DirectX, and was not used in 
the code. At this stage, 2 new unresolved extern symbols show up 
(_IID_IDirectXFileData & _IID_IDirectXFileDataReference). To correct this, add 
dxguid.lib to the project's dependencies.

3. Music: Several Linker 2005 errors created by several dual-defined variables 
in LIBCMTD.lib and MSVCR90.dll. For example, error LNK2005: __amsg_exit already 
defined in msvcrt.lib(MSVCR90.dll). The solution is to remove msvcrt.lib from 
the project's dependencies.

4. Setup: iweardrv.h not found. Apparently, this is part of a iWear VR920 
module, which is completely separate and not included. So, what's a dependency 
on it doing here??? The solution for this is to remove everything under the 
Wrap920 directory under the Setup subdirectory, and to comment out line 24 
(#define VR920SUPPORT) in CGfxC.cpp.

What version of the product are you using? On what operating system?
Visual Studio 2008 on Windows XP Pro

Please provide any additional information below.

Original issue reported on code.google.com by pcowe...@yahoo.com on 1 Dec 2013 at 9:23

GoogleCodeExporter commented 8 years ago
This was fixed in r106.

Original comment by pcowe...@yahoo.com on 30 Dec 2013 at 2:50