Unresolved externals while executing --compile-cxx on sample

[compile0219]

Fresh (for this even) Windows 7 install. Tried running 32-bit mode on a 64-bit Windows 7 install, then due to it not liking that if I didn't run it in that mode (but working, but doing the same thing it does now), I just did a fresh 32-bit install instead to simplify this process as much as possible without any extra commands. Obviously I don't get the error relating to the 64-bit system as it's now on a 32-bit system, however I am getting another error which they both shared.

I did copy this over from the other drive (which was also just as fresh, just 64-bit) however all of the software installs are also fresh. It did this on both versions of Windows.

So basically, everything but this was done on a 64-bit system, and now I have moved it all (with freshly reinstalled third party programs, like the SDK) to a 32-bit system. If I started over and compiled Panda3D on this version of Windows 7 would it make a difference? Didn't seem to matter during the compilation of that at all, but would it have an effect now?

Takes about 50 seconds of spewing out these to get to the bottom. I've compiled Panda3D (and ran postbuild), pythonembed, AES, did --make-nri, all successfully. Basically the last step of everything and it finally fails.

Screenshot: http://i.imgur.com/JNWFlb4.png

Using "python -OO make.py --compile-cxx" in the Windows 7 x86 Debug Build Environment command window.

[loblao]

It looks like there's something wrong with pythonembed. Could you zip and upload it?

[compile0219]

Alright, thanks. Here you go.

pythonembed.zip

[compile0219]

Just rebuilt it (might have done something wrong in the command line with cmake previously), looks like it doubled the file size x2. Going to give it a whirl.

[compile0219]

Now down to 2, hooray: http://i.imgur.com/FYLettw.png

Want the file again?

[compile0219]

Any ideas?

[loblao]

Please send your file.

[compile0219]

Sorry for the long delay. Here is the file.

pythonembed.zip

[compile0219]

Hey loblao, any updates on this? Thanks so much! @loblao

I could supply you with my pythonembed, it has nothing wrong with it from what I can tell.

[compile0219]

That would be great. Thanks!

pythonembed.zip
Here you go!
If it doesn't work, I won't be able to help, unfortunately. The reason Nirai doesn't offer precompiled binaries is due to compatibility issues.
This pythonembed was compiled on a 64-bit machine running Windows 10.

[padlocks]

Any help would be appreciated. I get these errors when I try to compile some source.
I have looked through other issues and couldn't find any use for them, the pythonembeded.lib you sent fixes 2 of the unresolved external symbols, but not all 7. I built mine as a win32 application, if any more information is needed please let me know.

"E:\Panda3D-1.10.0\python\ppython.exe" -OO make.py -cnm

Compiling CXX codes...
aes.cxx
main.cxx
stride.cxx
Linking...
Creating library built/infinity.lib and object built/infinity.exp
main.obj : error LNK2001: unresolved external symbol _initdirect
main.obj : error LNK2001: unresolved external symbol "void __cdecl init_libmotiontrail(void)" (?init_libmotiontrail@@yaxxz)
main.obj : error LNK2001: unresolved external symbol _initcore
stride.obj : error LNK2001: unresolved external symbol _initlibpandadna
stride.obj : error LNK2001: unresolved external symbol "void __cdecl init_libpandadna(void)" (?init_libpandadna@@yaxxz)
built/infinity.exe : fatal error LNK1120: 5 unresolved externals

@emiily Download the Nirai panda source again, and edit compile.bat and remove --no-pandatool and --static, and for faster build times, go ahead and add --no-eigen (optional). Now, you're going to need libpandadna. Extract the source into desktop, and edit CMakeLists.txt and change the panda3d directory to where your freshly built non static Panda3d is (the built folder in that new p3d), and cmake it. Then in that project directory (after building it with VS2010 (Set build mode to release!)), copy the libpandadna.dir directory to your build folder. On line 111 of make.py (If you're using Stride, which you are), add this line: compiler._built |= set(glob.glob('libpandadna.dir/Release/*.obj')). For the other errors, make sure your local version of Nirai (build/nirai/src) is up-to-date, as the other errors have been fixed.

[padlocks]

@lolman8776 I attached my BuildLog in a zip file. I'm trying to build libpandadna, I get 4 errors.

Incase it's something else, I get 25 unresolved externals. I put a file showing the logs in the zip

(For some reason I couldn't attach my zip file, so go here to download it.)

You need to build your actual stride.cxx executable on the NORMAL panda3d (the one that you didn't modify the compile.bat for), and build libpandadna against the one you DID modify compile.bat for. I can give you my .obj files for Libpandadna, too. But, if it doesn't work, I can't help you and it must be because of compatibility issues. I have attached the obj files. Extract the libpandadna.dir folder into your build directory (The same directory as your make.py).
libpandadna.zip