Game Development Community

No public symbols found

by John Kirby · in Technical Issues · 12/01/2008 (4:50 pm) · 5 replies

I am getting these five warnings when I compile with VS 2008 Std. There are no errors or failures.

Warning LNK4221: no public symbols found; archive member will be inaccessible. File=OPC_Picking.obj
Warning LNK4221: no public symbols found; archive member will be inaccessible. File=OPC_Common.obj
Warning C4505: 'yyunput' : unreferenced local function has been removed. File = CMDScan.cpp
Warning C4005: 'alloca' : macro redefinition. File = cmdgram.y
Warning C4701: potentially un initialized local variable 'yyval' used. File = bison.simple

After compiling and running the executable the game screen is completely black after the lighting loads. I have not added any code. This is a generated file from the Template. I have also tried compiling stronghold as a test and had the same problem.

Does anyone have an idea what may be causing this problem?

Thanks in advance for you help.
NextNext Thread
PrevPrevious Thread
More from Technical Issues


Torque Owner John Kirby
#1
12/01/2008 (9:22 pm)
Here's some additional information.

Before I reinstalled my pc I was running VS 2008 Pro on XP SP3 and TGEA 1.7.1 compiled just fine. I had to switch VS licenses with my business partner because he needed the Pro addition for another project so I'm stuck with VS Std and need to get this working. I also low leveled the hard drive before the reinstall and tried with another fresh install on a new hard drive tonight just in case.

I tried compiling with the 12-07 version of DX9 SDK and the most recent 12-08 version and have the same problem. Sound does work, but no graphics. I updated my Nvidia drivers to the latest rev, but still have made no progress.

I also tried using the Server 2003 Platform SDK instead of the one that comes with VS, but have not been able to fix the problem.

I tried compiling with MS Windows and Visual Studio not updated, and with them both updated. My previous setup "before the reinstall" was running XP SP3 with VS updated to the latest security patches available.

The LNK4221 error on the MS knowledge base says that the if there are no public symbols the linker will fail and that the a dll should be used. I don't buy that explanation since TGEA compiled just fine with VS Pro, and the other more obvious fact that I appear to be the only one with a post on this forum for this particular problem. So I tried adding the /FORCE command line arg to the linker, but that did not work either.

Torque Owner John Kirby
#2
12/02/2008 (9:37 am)
Yet another peice if information.

When pressing F11 to get into the editor the screen is no longer black and everything looks fine. But, when I exit the editor, the screen goes black again.

I'm downloading the 1.8 beta and will try to compile it. I will post my results when finished.

Associate Michael Hall
Distracted...
#3
12/02/2008 (10:41 am)
What you describe with the black screen at startup that goes away when you enter the editor is from using the newer DirectX SDK. I had that problem when I updated but it went away when I rolled back to the March SDK. I have no idea about your symbol problems though.

Torque Owner John Kirby
#4
12/02/2008 (10:48 am)
Coolness! I'll try it.

Thanks Mike. I'll post my results when I'm finished.

Torque Owner John Kirby
#5
12/02/2008 (11:57 am)
The black screen has gone away after rolling back to the March DirectX SDK. As for the symbol warnings. What happens is that the linker will not link an object file that does not have public members. So I'm using the /FORCE command line option to force the linker to link the object files. As for the alloca and yyval warnings, I'm not sure. I will try searching the forums and see if someone else has run into these warnings at some point. If anyone knows and wants to post here to give me an answer that would be great also.

Other than the warnings, everything looks like its working properly. I will be adding artwork and code so I guess I'll know if there are any apparent problems. "I hope."

Thanks again for your help Mike.