Problem when compiling BULL
- Thread starter stmartin
- Start date
EmperorFool
Deity
But you use VC++ Toolkit 2003 to do the actual compilation and linking, right? VS 2008, which I use, just calls nmake from the PSDK which uses VC++ to do the compilation.
Also, I notice some of those paths have a / instead of a \. What's up with that? It seems random. In any case, this is failing during the clean command, so I recommend deleting the .obj files manually and do a normal build.
Also, I notice some of those paths have a / instead of a \. What's up with that? It seems random. In any case, this is failing during the clean command, so I recommend deleting the .obj files manually and do a normal build.
glider1
Deity
Thanks for all the generosity and sharing all this great code design with us. 
I'm compiling a version of RevDCM with Bug 4.0 and Bull 1.0. At this stage the compiler complains about two files because it cannot link them:
ximawnd.cpp
CvGame::takeJPEGScreenShot(std::string fileName) const
I've commented out the code in the entire ximawnd file and the code in the cvgame function and it links fine and seems to run well (early days). If I comment out the code in one or the other, it will not link either. I'm using VC2008 with Refar's instructions and have been using it for the last 18 months at least.
EDIT: The makefile has been updated for the cximage resources and code, the extra objects and CvBugOptions code files. The problem would appear to be minor and so there is no hurry. It will get sorted some how.
Cheers.
I'm compiling a version of RevDCM with Bug 4.0 and Bull 1.0. At this stage the compiler complains about two files because it cannot link them:ximawnd.cpp
CvGame::takeJPEGScreenShot(std::string fileName) const
I've commented out the code in the entire ximawnd file and the code in the cvgame function and it links fine and seems to run well (early days). If I comment out the code in one or the other, it will not link either. I'm using VC2008 with Refar's instructions and have been using it for the last 18 months at least.
EDIT: The makefile has been updated for the cximage resources and code, the extra objects and CvBugOptions code files. The problem would appear to be minor and so there is no hurry. It will get sorted some how.
Cheers.
EmperorFool
Deity
What are the linking errors you get? Can you paste the error messages here?
glider1
Deity
Thanks for the interest. If I uncomment CvGame::takeJPGScreenShot() I get these linker errors:
If I uncomment out the entire ximawnd.cpp file I have to rebuild from scratch to get the linker errors from it so will keep it simple for now. Attached is my makefile.
Thanks again!
Cheers
Spoiler :
If I uncomment out the entire ximawnd.cpp file I have to rebuild from scratch to get the linker errors from it so will keep it simple for now. Attached is my makefile.
Thanks again!
Cheers
EmperorFool
Deity
I set this up a while ago, but I think I may have had to add a new library to get the ximage stuff to link. I wish I had taken notes at the time (sigh), but check your VC++ 2003 Toolkit's lib folder. Do you have the library "MFC42D.DLL"? If not, download it and place it there. If so, let me know and I'll look for other libs. That one sounds very familiar to me though, and it's modified date is 2004, a year after the other libs in that folder.
glider1
Deity
Well you have done a superb job so the occasional slip in note taking is understandable with so much detail. That lib didn't work. Downloaded it and put it in the toolkit. The urgency is low for now because it looks like the RevDCM BUG+BULL SVN merge is working well from all reports. Would be nice to fix and probably it is a lib that is within the genuine vc2003 pro toolkit. I bet Jdog would be able to link it.
Cheers.
Cheers.
Afforess
The White Wizard
Just a question here. I've downloaded and added MFC42D.DLL to my 2003 Toolkit Lib folder, but I still get errors compiling a debug build. Normal builds work fine, but I need a debug build to check for crashes.
Here's the error:
Spoiler :
phungus420
Deity
- Joined
- Mar 1, 2003
- Messages
- 6,296
Same exact problem. I can compile a final release gamecore fine, but debug fails. This effects all RevDCM based mods because it's a problem with the latest RevDCM SVN. That's a large problem, because RevDCM is used as the core in RoM, LoR, Quote Capita, and Dune Wars to name a few. Glider told us to ask you EF, as he can't figure it out.
This is the error I get (assume it's the same as Afforess's):
I'm including the RevDCM source, including the makefile.
This is the error I get (assume it's the same as Afforess's):
Spoiler :
I'm including the RevDCM source, including the makefile.
EmperorFool
Deity
Take a look at the BULL makefile. Yes, I have totally restructured it, but the information should be in there. One difference I see is that these are the libs I use:
For debug builds I add msvcprt.lib because it's added automatically during release builds.
Here are the libs from your makefile:
Try adding those two libs. I have no idea why a normal release would work if this is the problem, though. Try adding msvcprt.lib to your debug release as well.
Code:
boost_python-vc71-mt-1_32.lib winmm.lib user32.lib [B]gdi32.lib Ole32.lib[/B]For debug builds I add msvcprt.lib because it's added automatically during release builds.
Here are the libs from your makefile:
Code:
boost_python-vc71-mt-1_32.lib winmm.lib user32.lib msvcprt.libTry adding those two libs. I have no idea why a normal release would work if this is the problem, though. Try adding msvcprt.lib to your debug release as well.
Afforess
The White Wizard
This isn't fixing it for me. 
And I need a Debug DLL, as I got a CTD in-game...
And I need a Debug DLL, as I got a CTD in-game...
EmperorFool
Deity
That has no effect for you? Remove "/INCREMENTAL" from the debug LDFLAGS.
phungus420
Deity
- Joined
- Mar 1, 2003
- Messages
- 6,296
No change. Same errors exactly. (would I need to do a full rebuild since the libraries changed in the makefile?, if so that takes me over two hours to check )
)
Afforess
The White Wizard
Okay, I tried that, same errors. My computer just took longer to get me the errors...
Afforess
The White Wizard
Save your computers time Phungus, I just recompiled, and got the same errors again.
EmperorFool
Deity
Since these are linking errors, there's no need to recompile. Just delete the CvGameCoreDLL.lib files before rebuilding. Given that you had errors, though, it probably wasn't even created.
I'm not sure what to say at this point. I never could get Refar's makefile to work for me. That's why I redid it for BULL. For one thing, it's a lot clearer to me, and there's less option duplication. Would it be possible to start with BULL's makefile and add to it the RevDCM source files rather than the other way around?
Here are the main differences:
I'm not sure what to say at this point. I never could get Refar's makefile to work for me. That's why I redid it for BULL. For one thing, it's a lot clearer to me, and there's less option duplication. Would it be possible to start with BULL's makefile and add to it the RevDCM source files rather than the other way around?
Here are the main differences:
- Paths at top include path to Civ4/BTS
- No need to copy boost and python libs/includes to your SDK folder; point to the original ones installed with BTS.
- No project vs global options. We have one project, no use complicating things.
- Commonalities between Debug and Final_Release extracted to general variables.
I get this error in VC 2008 when trying to merge BULL into my own dll:
If I compile using CodeBlocks, I get no errors and a flawlessly working dll. Does anyone know how to get around this in VC 2008? I have up to this point been able to compile in both CB and VC without issues (for almost a year now), so this is a first...
Code:
1>CvDLLWidgetData.obj : error LNK2019: unresolved external symbol "bool __cdecl getBugOptionBOOL(char const *,bool,char const *)" (?getBugOptionBOOL@@YA_NPBD_N0@Z) referenced in function "public: void __thiscall CvDLLWidgetData::parseHealthHelp(struct CvWidgetDataStruct &,class CvWStringBuffer &)" (?parseHealthHelp@CvDLLWidgetData@@QAEXAAUCvWidgetDataStruct@@AAVCvWStringBuffer@@@Z)If I compile using CodeBlocks, I get no errors and a flawlessly working dll. Does anyone know how to get around this in VC 2008? I have up to this point been able to compile in both CB and VC without issues (for almost a year now), so this is a first...
EmperorFool
Deity
getBugOptionBOOL() is a function in CvBugOptions.cpp. Make sure you add a build rule for CvBugOptions.obj and add it to the list of LINK_OBJS in the makefile for each build target.
phungus420
Deity
- Joined
- Mar 1, 2003
- Messages
- 6,296
We over at RevDCM are still unable to get a debug dll to compile using the cximage code. To get around that glider has cut the cximage source from the project, but this causes the advanced sentry icons to be removed. jdog5000 tried to build a makefile modeled on BULL's as a template, but no dice. The Final Release dll works fine, and the debug dll compiles using jdog's makefile, but it CTDs when trying to play, and when initializing python there are a slew of errors using the debug dll it creates (also the .pdb file is like 20 something MBs, whereas it should be around 70MB). I've included the RevDCM source with the working (but CxImage source removed) makefile, along with jdog's. EF, any chance you could look at this and see what is wrong with jdog's makefile? It almost works, it compiles, but the debug dll just doesn't work, also the final realease dll has no issues using it.
EmperorFool
Deity
Why would the extra sentry icons not work? The CxImage library is used only for taking a screenshot from Python. I'll see what happens when I try to compile it here. Maybe there's still another library that I added that you don't have.
Similar threads
