Build issues

C++ coding using Panda3D
#1

I’m trying to build Panda in a C++ Win32 console application, using Visual Studio 2008. When I try to build in debug mod, I’m told that the file python26_d.lib cannot be opened. When I build in release mode, I get a bunch of errors, starting with the panda iostream file.

I’ve addedthe following include directories to the project:
C:\Panda3D-1.5.4\include
C:\Panda3D-1.5.4\python\parser-inc
C:\Panda3D-1.5.4\python\include

And the following library directories:
C:\Panda3D-1.5.4\lib
C:\Panda3D-1.5.4\python\lib

Am I missing anything? What might cause these errors? I’ll provide more information as needed.

Thank you.

#2

Whut, do you have Python 2.6 installed? You shouldn’t, Panda installs its own copy of Python 2.5, so any other install can be conflicting there.

#3

I did already have python installed, but I’m not pointing visual studio to that directory. Any idea what I can do to fix it? I do need that version of Python installed, though.

#4

Okay, I got the debug to link properly by removing the other python directory from my environment variables.

I’m still getting some errors on both builds. They start with this:

Error	1	error C2059: syntax error : 'enum [tag]'	c:\panda3d-1.5.4\include\parser-inc\iostream	32	PandaTest
Error	2	error C2334: unexpected token(s) preceding '{'; skipping apparent function body	c:\panda3d-1.5.4\include\parser-inc\iostream	32	PandaTest
Error	3	error C2062: type 'long' unexpected	c:\panda3d-1.5.4\include\parser-inc\iostream	40	PandaTest
Error	4	error C2238: unexpected token(s) preceding ';'	c:\panda3d-1.5.4\include\parser-inc\iostream	40	PandaTest
Error	5	error C2062: type 'void' unexpected	c:\panda3d-1.5.4\include\parser-inc\iostream	52	PandaTest
[/quote]
#5

And in removing my include reference to C:\Panda3D-1.5.4\python\parser-inc , I now get this:

Error	129	fatal error LNK1104: cannot open file 'python25_d.lib'	PandaTest	PandaTest

I"m thinking maybe I"m not including the right things. Is there a list of the things that I need to include to get a panda project to compile successfully?

#6

Two points.

(1) You can’t make a debug build of Panda, unless you also go find or make a debug build of Python, and of all the other thirdparty libraries. Microsoft won’t let you mix-and-match debug and release builds in the same executable, so it all has to be the same. That’s what the _d means: it’s looking for a debug build of Python. So, restrict yourself to a release build unless you want to go build a bunch of additional stuff first.

(2) Don’t add the parser-inc directory to the include path. The files in there are not intended to be read by the compiler. The other directories are correct, though.

David

#7

Okay, I was including C:\Panda3D-1.5.4\python\lib, but what I needed was C:\Panda3D-1.5.4\python\libs. What a difference a letter makes.

It’ll build in release mode, but not debug mode, which I now see the post telling me that wouldn’t work. So there’s no way to access a debugger in a panda app? That seems a bit… bad.

#8

You can certainly debug a panda app built in release mode. The debugger is just a little less accurate, particularly for showing you the values of local variables (a lot of these get optimized away and don’t exist where the debugger can query them).

Or, you can build the whole world in debug mode. People have done this, it’s not outrageous. It just takes a while, and you have to be fairly comfortable with building C++ projects.

There might be another option. You might be able to build in release mode, but disable compiler optimizations even though you are in release mode. This should make the debugger accurate again, but you won’t be using the debug heap, which is what causes the conflict between mixing debug and release builds in a single application. This is kind of advanced, though, and you should know what you are doing if you fiddle with these settings.

David

#9

Ah, okay. I forgot that you can debug in release mode. I’d gotten burnt by the anomalies of doing that a while back and must have blocked the option out in my mind.

Thank you both for your help.

#10

That error is caused by this code:

ifdef _DEBUG

pragma comment(lib,“python25_d.lib”)

else

pragma comment(lib,“python25.lib”)

endif /* _DEBUG */

In pyconfig.h So if you write:

#undef _DEBUG

before including anything Panda3D you will link against the release build of Python which is actually ok.